WO2019196846A1 - 通信方法及装置 - Google Patents

通信方法及装置 Download PDF

Info

Publication number
WO2019196846A1
WO2019196846A1 PCT/CN2019/081974 CN2019081974W WO2019196846A1 WO 2019196846 A1 WO2019196846 A1 WO 2019196846A1 CN 2019081974 W CN2019081974 W CN 2019081974W WO 2019196846 A1 WO2019196846 A1 WO 2019196846A1
Authority
WO
WIPO (PCT)
Prior art keywords
event
terminal
service
function entity
message
Prior art date
Application number
PCT/CN2019/081974
Other languages
English (en)
French (fr)
Inventor
吴义壮
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to KR1020207031097A priority Critical patent/KR102486370B1/ko
Priority to BR112020020740-3A priority patent/BR112020020740A2/pt
Priority to EP19785700.6A priority patent/EP3764672A4/en
Publication of WO2019196846A1 publication Critical patent/WO2019196846A1/zh
Priority to US17/067,377 priority patent/US11523268B2/en
Priority to US17/983,019 priority patent/US20230056728A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/142—Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/53—Network services using third party service providers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/535—Tracking the activity of the user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a communication method and apparatus.
  • FIG. 1 A schematic diagram of a non-roaming architecture of an existing evolved packet system (EPS) as shown in FIG. 1 , in order to support a service capability server/application server (service capability server/) for installing a third-party application (such as a machine type application)
  • the application server, SCS/AS uses the EPS network to enhance the existing network architecture.
  • a service capability exposure function (SCEF) network element is introduced.
  • 3GPP 3rd generation partnership project
  • Machine-type services include a service that does not require high latency, that is, high-latency services.
  • an event of "availability after DDN failure” after monitoring "downlink data notification (DDN) failure” is defined. That is, the SCS/AS can subscribe to the 3GPP EPS network through the SCEF to monitor the "DDN Available After Notification” event.
  • DDN downlink data notification
  • the SCS/AS sends a data packet to the terminal through the EPS network, if the terminal is in an unavailable state, the EPS network will activate the "DDN Failed Available Notification” event, that is, monitor the status of the terminal: when the terminal enters the available state, the network passes the SCEF.
  • the terminal availability status is reported to the SCS/AS, so that the SCS/AS resends data to the terminal.
  • both session and mobility are controlled by a mobility management entity (MME).
  • MME mobility management entity
  • SGW serving gateway
  • MME initiates paging for the terminal, but does not receive a response, or the terminal is in a power saving mode (power saving Mode, PSM), or the terminal is in a mobile initiated connection only (MICO) mode, and the MME directly activates the monitoring event.
  • PSM power saving Mode
  • MICO mobile initiated connection only
  • 5G fifth generation
  • session management, mobility management and access are controlled by different functional entities. In this architecture, how the network configures the corresponding terminal event and activates the reporting event is an unresolved problem.
  • the present application provides a communication method and apparatus to implement subscription of terminal events in a 5G architecture.
  • a communication method comprising: determining a session management function entity according to at least one of a data network name, slice information, and an application function service identifier; and transmitting a first message to the session management function entity,
  • the first message is used to subscribe to a terminal event, and the first message includes service description information, where the service description information is used to indicate a service corresponding to the terminal event.
  • the session management function entity that manages the specific service subscribes to the terminal event, and the session management function entity manages the network configuration subsequent to the terminal event, so that the terminal event can be subscribed to the specific service under the 5G architecture.
  • the service description information is further used to determine an application function entity that provides a service for the terminal.
  • the service service may be provided to the terminal by one or more application function entities.
  • the service corresponding to the terminal event is indicated by the service description information, so that the application function entity that subscribes to the terminal event can be distinguished.
  • the first message further includes an event association identifier and event type information of the terminal event, where the event The association identifier is used to identify an association relationship between the terminal event and a function entity that subscribes to the terminal event, where the event type information is used to identify the terminal event.
  • the terminal management function entity subscribes to the terminal event
  • the event association identifier and the event type information are carried, and the function entity that subscribes to the terminal event can be identified according to the event association identifier, and the terminal event can be identified according to the event type information.
  • the type of event is carried
  • the method further includes: sending a second message to the access and mobility management function entity, where the second The message is used to subscribe to the terminal event, the second message includes an event association identifier and event type information of the terminal event, and the event association identifier is used to identify the terminal event and a functional entity that subscribes to the terminal event. The relationship between the events is used to identify the terminal event.
  • the event association identifier and the event type information are carried, and the function entity that subscribes to the terminal event can be identified according to the event association identifier, according to the event type information.
  • the method further includes receiving a third message from the application function entity, the third message is for subscribing to the terminal event, and the third message includes the service description information.
  • the application function entity may subscribe to the terminal event of the terminal to subscribe to the event, and when the terminal event is subscribed, the service corresponding to the terminal event is indicated by the service description information, so that the third-party application that subscribes to the terminal event can be distinguished.
  • the control function entity may be a network open function entity, a unified data management function entity or a policy control function entity.
  • the third message further includes at least one information: an identifier of the terminal corresponding to the terminal event, and a terminal event Event type information, the data network name, the slice information, and the application function service identifier.
  • the receiving, by the application, the third message including: receiving The third message forwarded by the network open function entity.
  • the method further includes: transmitting at least one of the service description information, the event association identifier, the identifier of the terminal, an event type of the terminal event, the data network name, the slice information, and the application function service identifier One to the consolidated database functional entity for storage.
  • related information of the subscription terminal event may be uniformly stored by the unified database function entity.
  • the method further includes: obtaining the service description information, the event association identifier, the identifier of the terminal, event type information of the terminal event, the data network name, and the slice information from a local or unified database function entity. And at least one of the application function service identifiers.
  • the method further includes: receiving the terminal event notification from an access and mobility management function entity or the session management function entity And sending the terminal event notification to the application function entity.
  • the access and mobility management function entity or the session management function entity opens the function entity through the network, and then the network open function entity notifies the application function entity to monitor the terminal event.
  • the event type of the terminal event includes a terminal available event after the downlink data notification fails.
  • a communication device having a function of implementing the behavior of a communication device in the above method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the communications apparatus includes: a processing unit, configured to determine a session management function entity according to at least one of a data network name, a slice information, and an application function service identifier; and a sending unit, configured to The session management function entity sends a first message, where the first message is used to subscribe to a terminal event, and the first message includes service description information, where the service description information is used to indicate a service corresponding to the terminal event.
  • the communication device includes a processor for coupling with a memory, reading and executing instructions in the memory to implement the above method.
  • the principle and the beneficial effects of the device can be referred to the method embodiments of the foregoing possible communication devices and the beneficial effects thereof. Therefore, the implementation of the device can refer to the implementation of the method, and the repetition is not Let me repeat.
  • a communication method comprising: receiving a first message sent by a session management function entity, the first message being used to subscribe to a terminal event; monitoring the subscribed terminal event; and when detecting the The terminal event notification is sent to the function entity that subscribes to the terminal event, where the terminal event notification includes at least one of the following: an identifier of the terminal corresponding to the terminal event and an event association identifier of the terminal event, The event association identifier is used to identify an association relationship between the terminal event and a functional entity that subscribes to the terminal event.
  • the access and mobility management function entity may receive a subscription of the terminal event of the session management function entity, and when the terminal event is detected, send a terminal event notification to the function entity that subscribes to the terminal event, thereby implementing the 5G architecture. Subscription and monitoring of terminal events.
  • a communication device having a function of implementing the behavior of a communication device in the above method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the communications apparatus includes: a receiving unit, configured to receive a first message sent by a session management function entity, where the first message is used to subscribe to a terminal event, and a monitoring unit, configured to monitor the subscribed And the sending unit, configured to: when the monitoring unit detects the terminal event, send the terminal event notification to a functional entity that subscribes to the terminal event, where the terminal event notification includes at least the following A message: an identifier of the terminal corresponding to the terminal event and an event association identifier of the terminal event, where the event association identifier is used to identify an association relationship between the terminal event and a functional entity that subscribes to the terminal event.
  • the communication device includes a processor for coupling with a memory, reading and executing instructions in the memory to implement the above method.
  • the principle and the beneficial effects of the device can be referred to the method embodiments of the foregoing possible communication devices and the beneficial effects thereof. Therefore, the implementation of the device can refer to the implementation of the method, and the repetition is not Let me repeat.
  • a fifth aspect provides a communication method, including: receiving a notification that a session management function entity or a control function entity sends a monitoring terminal reachable event; monitoring a terminal reachable event; and when detecting the reachable event of the terminal, The session management function entity or the control function entity sends a terminal reachability notification, and the terminal reachability notification is used for monitoring the terminal available event after the downlink data notification fails.
  • the session management function entity can perform monitoring of the terminal available events after the downlink data notification fails.
  • the access and mobility management function entity notifies the session management function entity when the terminal is reachable, thereby activating the session management function entity to monitor the terminal available events after the downlink data notification fails, thereby implementing subscription of the terminal event in the 5G architecture. monitor.
  • a communication device having a function of implementing the behavior of a communication device in the above method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the communication device includes: a receiving unit, configured to receive a notification that the session management function entity sends a monitoring terminal reachable event; a monitoring unit, configured to monitor the terminal reachable event; and a sending unit, configured to: When the monitoring unit detects the reachable event of the terminal, the terminal management reachable notification is sent to the session management function entity, and the terminal reachable notification is used for monitoring the terminal available event after the downlink data notification fails.
  • the communication device includes a processor for coupling with a memory, reading and executing instructions in the memory to implement the above method.
  • the principle and the beneficial effects of the device can be referred to the method embodiments of the foregoing possible communication devices and the beneficial effects thereof. Therefore, the implementation of the device can refer to the implementation of the method, and the repetition is not Let me repeat.
  • the seventh aspect provides a communication method, including: instructing a user plane function entity to perform service detection, where the service is a service corresponding to a subscribed terminal event; and receiving a service detection notification sent by the user plane function entity, The service detection notification is used to indicate the occurrence of the service data; and in response to the service detection notification, send a notification to the access and mobility management function entity or the control function entity to monitor the terminal event.
  • the session management function entity that manages the specific service subscribes to the terminal event, and the session management function entity notifies the access and mobility management function entity to monitor the terminal event when receiving the service detection notification of the user plane function entity. Therefore, in the 5G architecture, terminal events can be subscribed and monitored for specific services.
  • the user plane function entity is configured to perform service detection, including: indicating that the user plane function entity does not store access network tunnel information for transmitting the service data Or performing service detection when the user plane tunnel information is downlinked; or instructing the user plane function entity to perform service detection notification when the access network tunnel information or the downlink user plane tunnel information for transmitting the service data is not stored.
  • the method further includes: receiving, by the control function entity, a first message, where the first message is used Indicating the service, the first message includes service description information of the service.
  • the subscription of the terminal event of the control function entity is received, and when the terminal event is subscribed, the service corresponding to the terminal event is indicated by the service description information, so that the third-party application that subscribes to the terminal event can be distinguished.
  • the first message is further used to subscribe to the terminal event, and the first message includes an event association of the terminal event
  • the identifier and the event type information are used to identify an association relationship between the terminal event and a function entity that subscribes to the terminal event, where the event type information is used to identify the terminal event.
  • the terminal management function entity subscribes to the terminal event
  • the event association identifier and the event type information are carried, and the function entity that subscribes to the terminal event can be identified according to the event association identifier, and the terminal event can be identified according to the event type information.
  • the type of event is carried
  • the terminal event includes a terminal available event after the downlink data notification fails, and the method further includes: receiving the access and the mobile If the terminal reachable notification or the downlink data notification is sent by the sexual management function entity, the terminal may notify the event; and after the downlink data notification fails, the terminal may notify the network to open the function entity or the application function entity.
  • the method further includes: receiving, by the local session management function entity, the first message, the first message The device is used to indicate the service, and the first message includes service description information of the service.
  • the subscription of the terminal event of the local session management function entity is received, and when the terminal event is subscribed, the service corresponding to the terminal event is indicated by the service description information, so that the third-party application that subscribes to the terminal event can be distinguished.
  • a communication device having a function of implementing the behavior of a communication device in the above method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the communication device includes: a sending unit, configured to instruct a user plane function entity to perform service detection, where the service is a service corresponding to a subscribed terminal event, and a receiving unit, configured to receive the user a service detection notification sent by the surface function entity, where the service detection notification is used to indicate the occurrence of the service data; and the sending unit is further configured to send to the access and mobility management function entity in response to the service detection notification A notification of the terminal event is monitored.
  • the communication device includes a processor for coupling with a memory, reading and executing instructions in the memory to implement the above method.
  • the principle and the beneficial effects of the device can be referred to the method embodiments of the foregoing possible communication devices and the beneficial effects thereof. Therefore, the implementation of the device can refer to the implementation of the method, and the repetition is not Let me repeat.
  • the ninth aspect provides a communication method, including: receiving a first message sent by a session management function entity, where the first message is used to indicate that the service is detected, and the service is a service corresponding to the subscribed terminal event; And detecting, by the first message, the service; and sending a service detection notification to the session management function entity, where the service detection notification is used to indicate the occurrence of the service data.
  • the service detection indication of the session management function entity when the service data is received, the service corresponding to the subscribed terminal event is detected, and the session management function entity is notified to implement subscription and monitoring of the terminal event in the 5G architecture.
  • the detecting, according to the first message includes: according to the first message, when an access for transmitting the service data is not stored When the network tunnel information is detected, the service is detected.
  • a communication device having a function of implementing the behavior of a communication device in the above method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the communications apparatus includes: a receiving unit, configured to receive a first message sent by a session management function entity, where the first message is used to indicate that the service is detected, and the service is a subscribed terminal. a service corresponding to the event, a detecting unit, configured to detect the service according to the first message, and a sending unit, configured to send a service detection notification to the session management function entity, where the service detection notification is used to indicate the The occurrence of business data.
  • the communication device includes a processor for coupling with a memory, reading and executing instructions in the memory to implement the above method.
  • the principle and the beneficial effects of the device can be referred to the method embodiments of the foregoing possible communication devices and the beneficial effects thereof. Therefore, the implementation of the device can refer to the implementation of the method, and the repetition is not Let me repeat.
  • the eleventh aspect provides a communication method, including: instructing a user plane function entity to perform service detection, where the service is a service corresponding to a terminal event subscribed by the first application function entity; and receiving a service sent by the user plane function entity Detecting a notification, the service detection notification is used to indicate data of detecting the service; when the terminal is unreachable, monitoring the terminal event according to the service detection notification; and opening to the network when the terminal event is detected
  • the functional entity or the first application function entity sends a terminal event notification.
  • the session management function entity instructs the user plane function entity to detect a specific service, and when the terminal is unreachable, monitors the terminal event according to the service detection notification sent by the user plane function entity, and sends the terminal when the terminal event is detected. Event notification, so that terminal events can be subscribed and notified for specific services under the 5G architecture.
  • the terminal event includes a terminal available event or a terminal reachable event after the downlink data notification fails.
  • the monitoring the terminal event is a terminal reachable event sent by the access and mobility management function entity Notification or downlink data transmission failure terminal available event notification.
  • the method further includes: when receiving And receiving the downlink data transmission failure notification sent by the mobility management function entity, or receiving the unreachable notification sent by the access and mobility management function entity before detecting the service, determining that the terminal is unreachable.
  • the terminal is unreachable, and may receive the downlink data failure notification sent by the AMF, or the other application function entity may receive the unreachable notification from the AMF when transmitting the service data.
  • the method further includes: receiving a first message sent by a local session management function entity, where the first message is used to indicate The service and the subscription to the terminal event, the first message includes service description information of the service, an event association identifier of the terminal event, and event type information, where the event association identifier is used to identify the terminal event and And an association relationship between the functional entities of the terminal event, where the event type information is used to identify the terminal event.
  • terminal event monitoring may be performed by an access network session management function entity.
  • a communication apparatus having a function of realizing the behavior of a communication apparatus in the method of the eleventh aspect described above.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the communication device includes: an indication unit, configured to instruct a user plane function entity to perform service detection, where the service is a service corresponding to a terminal event subscribed by the first application function entity, and a receiving unit is configured to: Receiving a service detection notification sent by the user plane function entity, where the service detection notification is used to indicate data of the service is detected; and the monitoring unit is configured to monitor the terminal according to the service detection notification when the terminal is unreachable And an sending unit, configured to send a terminal event notification to the network open function entity or the first application function entity when the terminal event is detected.
  • the communication device includes a processor for coupling with a memory, reading and executing instructions in the memory to implement the above method.
  • the principle and the beneficial effects of the device can be referred to the method embodiments of the foregoing possible communication devices and the beneficial effects thereof. Therefore, the implementation of the device can refer to the implementation of the method, and the repetition is not Let me repeat.
  • a communication method including: receiving a first message of a terminal event sent by a control function entity, where the first message is used to subscribe to a terminal event, and the first message includes service description information and Data network name/single network slice selection assistance information DNN/S-NSSAI; sending a second message to the session management function entity, wherein the second message is for subscribing to a service detection event, and the second message includes the service description Receiving a service detection notification from the session management function entity; activating the terminal event when the terminal is unreachable; and transmitting the terminal reachable to the capability open node or the application function entity when detecting that the terminal is reachable Notice.
  • the sending the second message to the session management function entity includes: when the DNN/S-NSSAI of the session is the same as the DNN/S-NSSAI included in the first message, to the session management function The entity sends the second message.
  • the sending the second message to the session management function entity comprises: sending a subscription request to the local session management function entity or the roaming session management function entity; or to the local session management function entity or the roaming session management function The entity sends a session context update request for subscribing to the terminal event.
  • a communication method comprising: receiving a second message of a terminal event from a mobility management function entity AMF; and transmitting a third message to the user plane function entity UPF, the third message being used to indicate
  • the service detects that the service is a service corresponding to the subscribed terminal event; receives a service detection notification from the user plane function entity, where the service detection notification is used to indicate the occurrence of the service data; and the mobility management The functional entity sends the service detection notification.
  • the receiving, by the second message from the mobility management function entity, a second message comprising: receiving a session context update request from the mobility management function entity, the session context update request for subscribing to the Terminal event.
  • sending the third message to the user plane function entity includes: sending the third message to the user plane function entity during or after the PDU session deactivation process, where the third message is used to indicate that the service is performed.
  • the service is detected as a service corresponding to the subscribed terminal event.
  • a communication method comprising: receiving a first message from a control function entity, the first message is used to subscribe to a terminal event, and the first message includes service description information, where the service The description information is used to indicate a service corresponding to the terminal event.
  • the method before receiving the service information of the user function entity, the method includes: sending a service information request to the user function entity.
  • the sending the service information request to the user function entity includes: if the downlink data notification fails, sending a service information request to the user function entity.
  • the event association information is sent to the mobility management entity or the capability opening entity, where the event association information is used to determine event reporting information, including: performing mobility management according to the service description information and the service information.
  • the entity or capability open entity sends event association information, and the event association information is used to determine event reporting information.
  • a communication apparatus having the function of implementing the behavior of the communication apparatus in the method of any one of the thirteenth aspect to the fifteenth aspect.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the communication device includes: an indication unit, configured to instruct a user plane function entity to perform service detection, where the service is a service corresponding to a terminal event subscribed by the first application function entity, and a receiving unit is configured to: Receiving a service detection notification sent by the user plane function entity, where the service detection notification is used to indicate data of the service is detected; and the monitoring unit is configured to monitor the terminal according to the service detection notification when the terminal is unreachable And an sending unit, configured to send a terminal event notification to the network open function entity or the first application function entity when the terminal event is detected.
  • the communication device includes a processor for coupling with a memory, reading and executing instructions in the memory to implement the above method.
  • the principle and the beneficial effects of the device can be referred to the method embodiments of the foregoing possible communication devices and the beneficial effects thereof. Therefore, the implementation of the device can refer to the implementation of the method, and the repetition is not Let me repeat.
  • a computer readable storage medium is provided, the instructions being stored in a computer readable storage medium, when executed on a computer, causing the computer to perform the methods described in the above aspects or any implementations.
  • a computer program product comprising instructions for causing a computer to perform the method of any of the above aspects or any implementations when executed on a computer is provided.
  • FIG. 1 is a schematic diagram of an existing EPS non-roaming architecture
  • FIG. 2 is a schematic structural diagram of an interface in a 3GPP EPS network architecture opened by SCEF;
  • FIG. 3a is a schematic diagram of a 5G service-based interface-based non-roaming architecture
  • Figure 3b is a schematic diagram of a 5G reference point based non-roaming architecture
  • FIG. 4 is a schematic flowchart of an application function entity configuring a subscription terminal event to a network according to an embodiment of the present disclosure
  • FIG. 5a is a schematic flowchart of an example in which an AF configures a subscription terminal event to a UDM/PCF through an NEF;
  • FIG. 5b is a schematic flowchart of an example of an AF configuring a subscription terminal event to a UDR through a PCF;
  • FIG. 5c is a schematic flowchart of an example of an AF configuring a subscription terminal event to a UDR through an NEF;
  • FIG. 6 is a schematic flowchart of a communication method according to an embodiment of the present application.
  • FIG. 6b is a schematic flowchart diagram of another communication method according to an embodiment of the present application.
  • 6c is a schematic flowchart of a NEF performing terminal event notification according to a specific example
  • FIG. 7a is a schematic flow chart of an exemplary communication method
  • FIG. 7b is a schematic flowchart of another example communication method
  • FIG. 7c is a schematic flowchart of still another example communication method
  • FIG. 7d is a schematic flowchart of still another example communication method
  • FIG. 8 is a schematic diagram of a module of a communication device according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of another communication device according to an embodiment of the present disclosure.
  • FIG. 9b is a schematic diagram of still another module of a communication device according to an embodiment of the present application.
  • FIG. 10 is a schematic diagram of still another module of a communication device according to an embodiment of the present application.
  • FIG. 11 is a schematic block diagram of still another communication device according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of hardware of a communication device according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic flowchart diagram of still another communication method provided by an embodiment of the present application.
  • 15 is a schematic block diagram of still another communication device according to an embodiment of the present application.
  • FIG. 16 is a schematic flowchart diagram of still another communication method according to an embodiment of the present application.
  • FIG. 17 is a schematic flowchart diagram of still another communication method according to an embodiment of the present application.
  • FIG. 18 is a schematic flowchart diagram of still another communication method according to an embodiment of the present application.
  • FIG. 19 is a schematic flowchart diagram of still another communication method according to an embodiment of the present application.
  • FIG. 20 is a schematic flowchart diagram of still another communication method according to an embodiment of the present application.
  • the technical solution of the present application can be applied to the non-roaming architecture of the EPS network shown in FIG. 1 , and can also be applied to the roaming architecture of the EPS network; and can also be applied to the non-roaming architecture and the roaming architecture of the next generation network, for example, for example, , in the non-roaming architecture based on the serviced interface of the fifth generation mobile communication network as shown in FIG. 3a, and in the 5G reference point based non-roaming architecture as shown in FIG. 3b.
  • the communication system mainly includes an access and mobility management function (AMF) entity and a session management function (SMF). Entity, user plane function (UPF) entity, network exposure function (NEF) entity, and application function (AF) entity. It may also include a policy control function (PCF) entity, a unified data repository (UDR) entity, and a unified data management (UDM) functional entity.
  • AMF access and mobility management function
  • SMF session management function
  • Entity user plane function
  • NEF network exposure function
  • AF application function
  • PCF policy control function
  • UDR unified data repository
  • UDM unified data management
  • AMF entity mainly responsible for the processing of signaling, such as access control, mobility management, attach and detach, and gateway selection.
  • the AMF entity provides a service for the session in the terminal
  • the storage resource of the control plane is provided for the session to store the session identifier, the SMF entity identifier associated with the session identifier, and the like.
  • SMF entity mainly responsible for session management, specifically responsible for user plane functional entity selection, user plane function entity redirection, internet protocol (IP) address allocation, bearer establishment, modification and release, and quality of service , QoS) control.
  • IP internet protocol
  • UPF entity responsible for forwarding and receiving user data in the terminal.
  • the user data may be received from the data network and transmitted to the terminal through the access network device.
  • the user data may also be received from the terminal through the access network device and forwarded to the data network.
  • the transmission resources and scheduling functions for serving the terminal in the UPF entity are managed and controlled by the SMF entity.
  • NEF entity mainly supports 3GPP network and third-party applications for secure interaction. NEF can securely open network capabilities and events to third-party applications to enhance or improve application service quality. The 3GPP network can also securely obtain relevant data from third-party applications to enhance intelligent decision-making of the network. Recover structured data from UDR or store structured data in UDR.
  • AF entity Major support network interacts with the 3GPP to provide services, such as impact data routing decisions, policy control function, or provide some business services (these services may be a third party (3 rd party) on the network side, a third party may not be of).
  • services such as impact data routing decisions, policy control function, or provide some business services (these services may be a third party (3 rd party) on the network side, a third party may not be of).
  • PCF entity mainly supports providing a unified policy framework to control network behavior, providing policy rules to the control layer network function, and being responsible for obtaining user subscription information related to policy decisions.
  • UDR entity It is mainly responsible for storing structured data.
  • the stored content includes subscription data and policy data, externally exposed structured data and application-related data.
  • UDM entity mainly used to manage user subscription information.
  • the above functional entity is only a name, and the name itself does not limit the entity.
  • the session management function entity may also be replaced with a "session management function" or other name.
  • the session management function entity may also correspond to an entity that includes other functions in addition to the session management function.
  • the user plane function entity may also be replaced with a "user plane function” or other name, and the user plane function entity may also correspond to an entity including other functions in addition to the user plane function.
  • the terminal accesses the network through a radio access network (RAN) device or an access network (AN) device.
  • the RAN device is mainly a wireless network device in a 3GPP network
  • the AN may be an access network device defined by non-3GPP.
  • the terminal may be a user equipment (UE), a handheld terminal, a notebook computer, a subscriber unit, a cellular phone, a smart phone, a wireless data card, and a personal number.
  • UE user equipment
  • handheld terminal a notebook computer
  • subscriber unit a cellular phone
  • smart phone a wireless data card
  • personal number personal digital assistant (PDA) computer
  • tablet computer wireless modem
  • handheld laptop computer
  • cordless phone or wireless local loop , WLL
  • MTC machine type communication
  • the terminal can communicate with the radio access network (RAN) device by using some air interface technology.
  • the RAN device is mainly responsible for radio resource management, QoS management, data compression, and encryption on the air interface side.
  • the access network device may include various forms of base stations, such as a macro base station, a micro base station (also referred to as a small station), a relay station, an access point, and the like.
  • the names of devices with base station functions may vary, for example, in a 5G system, called gNB; in a long term evolution (LTE) system, It is an evolved Node B (eNB or eNodeB); in a 3rd generation (3G) system, it is called a Node B or the like.
  • the AN device allows non-3GPP technology interworking between the terminal and the 3GPP core network, for example, non-3GPP technologies such as: wireless fidelity (Wi-Fi), worldwide interoperability for microwave access (WiMAX) ), code division multiple access (CDMA) network, and the like.
  • non-3GPP technologies such as: wireless fidelity (Wi-Fi), worldwide interoperability for microwave access (WiMAX) ), code division multiple access (CDMA) network, and the like.
  • the terminal is in an unavailable state, that is, the network initiates paging for the terminal, but does not receive a response, or the terminal is in the PSM mode, or the terminal is in the MICO only mode, and the like.
  • the PSM mode refers to allowing the terminal to reduce energy loss and cannot immediately reach the service data sent to the terminal.
  • the MICO mode means that only the terminal is allowed to initiate a connection.
  • the DDN failure may be that the network detects that the terminal is in an unavailable state, or triggers the priority of the DDN data (ie, the allocation and retention priority (ARP), which is not higher than the previously triggered DDN.
  • ARP allocation and retention priority
  • a terminal event may be an event that requires various types of status or information to be obtained from the network.
  • the technical solution of the present application can be applied to a scenario of high-latency communication, and the terminal event may be a terminal available event after the DDN fails.
  • the application function entity providing the high-latency communication service can support the service communication with low delay requirement by subscribing to the terminal available event after the DDN failure.
  • the terminal event can also be a terminal reachable event or the like.
  • the application function entity installs related applications to provide corresponding services or services.
  • a subscription to a terminal event refers to subscribing to an event notification or modifying an already subscribed event through a service operation.
  • system and “network” in the embodiments of the present application may be used interchangeably.
  • Multiple means two or more.
  • a plurality can also be understood as “at least two” in the embodiment of the present application.
  • the character "/” unless otherwise specified, generally indicates that the contextual object is an "or" relationship.
  • the embodiment of the present application provides a communication method and apparatus, for a session management function entity that manages a specific service, to subscribe to a terminal event, and the session management function entity notifies the access and the mobile when receiving the service detection notification of the user plane function entity.
  • the sexual management function entity monitors terminal events so that in the 5G architecture, terminal events can be subscribed and monitored for specific services.
  • the subscribing to the network event of the application and the activation of the terminal event and the notification of the terminal event mainly include two processes:
  • the application function entity with the application installed first configures the terminal event to the network.
  • the configuration path can be as follows: AF configures events to the UDM/PCF through the NEF; the AF configures events to the UDR through the PCF; and the AF configures events to the UDR through the NEF. This will be described in detail below.
  • the network activates the terminal event and notifies the terminal event. This will be described later through a detailed communication method flow.
  • FIG. 4 a schematic flowchart of an application function entity configuring a subscription terminal event to a network according to an embodiment of the present application, the method may include the following steps:
  • the application function entity sends a first message to the control function entity.
  • the control function entity receives the first message from the application function entity.
  • the first message is used to subscribe to a terminal event, and the first message includes service description information.
  • the first message further includes at least one of the following: an identifier of the terminal corresponding to the terminal event, event type information of the terminal event, a data network name, a slice information, and an application function service identifier.
  • the control function entity allocates an event correlation identifier of the terminal event.
  • the unified database function entity stores at least one of the foregoing information.
  • This embodiment takes 5G as an example.
  • the application function entity that provides the service service may send a first message to the control function entity, where the first message is used to subscribe to the terminal event to the network.
  • the control function entity may be a UDM, a PCF or an NEF or the like.
  • the control function entity receives the first message.
  • the subscription of the terminal event to the network may be one or more application function entities.
  • the services corresponding to the terminal events subscribed by the multiple application function entities may be the same or different.
  • multiple application function entities may subscribe to the same terminal event to multiple terminals, or multiple application function entities may subscribe to different terminal events to the same terminal.
  • the service description information is carried in the first message.
  • the service description information is used to indicate a service corresponding to the terminal event.
  • the service description information may be description information of the service data.
  • the service description information may be an IP triplet (destination IP address/IPv6 prefix (IPv6 prefix), port number, IP upper layer protocol number (such as transport protocol)), or application identifier (application ID), or non-IP ( Non-IP) descriptor, or Ethernet service description information, and any description information of a service that can identify a specific application function entity.
  • the destination IP address may be a destination IPv4 address, a destination IPv6 prefix, or a destination IPv6 address.
  • the related functional entity may distinguish the multiple application functional entities according to the service description information.
  • the first message further includes at least one of the following information: an identifier of the terminal corresponding to the terminal event, event type information of the terminal event, a data network name (DNN), a slice information, and an application function service identifier (application function service) Identifier, AF-service-ID).
  • the identifier of the terminal may be an identifier of a single terminal (UE ID), or may be a group ID of multiple terminals (ie, a group).
  • the terminal identifier may be a common public subscription identifier (GPSI) or the like for identifying the user.
  • GPSI public subscription identifier
  • the group identity can be an external group identity.
  • the terminal event may be an event that needs to acquire various types of status or information from the network, and the event type of the terminal event may also be a defined type of terminal event. Event type information is used to identify the terminal event.
  • the technical solution of the present application can be applied to a scenario of high-latency communication, and the event type of the terminal event may be a terminal available event after the downlink data notification fails.
  • the terminal available event after the downlink data notification fails means that when the application function entity sends a downlink data packet to the terminal through the network, if the terminal is in an unavailable state, the network activates the event and monitors the state of the terminal. When the terminal enters an available state, the network reports the terminal available state to the application function entity through the control function entity.
  • the event type of the terminal event may also be a terminal reachable event or the like.
  • the event type of the terminal event may also be a service detection event, which is used to subscribe to the network to notify the subscriber when the service occurs.
  • the event type information may be represented by an index number of an event type specified by the protocol, and the event type information is stored in advance in the network device and the terminal device.
  • the DNN is used to identify the data network accessed by the user.
  • the slice information may be a slice instance and/or single network slice selection assistance information (S-NSSAI).
  • S-NSSAI or slice instance is used to select a specific slice network, ie a network of core networks, such as SMF and UPF.
  • the AF-Service-id is an identifier of an application function service, and the network side can derive DNN and slice information according to the identifier.
  • the first message may further include a notification target address.
  • the notification destination address can be NEF ID, AF ID or AF address.
  • the control function entity receives the first message, and processes the first message, including checking, according to the local policy, whether the application function entity is authorized to perform the service request, whether the first message has a problem, and whether the request of the application function entity exceeds the limit. Or exceed the request frequency and so on. If the check passes, the control function entity stores the above information and assigns an event correlation identifier of the terminal event.
  • the event association identifier is used to identify an association relationship between a terminal event and a functional entity that subscribes to the terminal event.
  • the event correlation identifier may also be referred to as a notification correlation ID.
  • the event association identifier may also be a subscription correlation ID, and the subscription association identifier may be allocated by an AMF or an SMF.
  • the notification target address can be used in conjunction with the notification association ID: the notification destination address and the notification association ID are used to associate the notification received from the event provider with the subscription. A subscription and a separate notification destination address are associated with the notification association ID.
  • control function entity may also send a message to the UDM/PCF to subscribe to the terminal event.
  • the message includes service description information, and further includes at least one of the following: an identifier of the terminal corresponding to the terminal event, event type information of the terminal event, DNN, slice information, and an application function service identifier.
  • control function entity checks whether the message is valid, including checking whether the network supports event monitoring, whether the request is in the received range, and the like.
  • the control function entity stores the above information when the check is passed.
  • control function entity may also send the above information to the UDR for unified storage by the UDR.
  • control function entity sends the service description information, or the event association identifier, or the identifier of the terminal, or the event type information of the terminal event, or the data network name, or the slice information, or the application function service identifier, or any of the above two Combination, or a combination of any three of the above, or a combination of any of the above, or a combination of any of the above five, or a combination of any of the above six, or the above seven to a consolidated database functional entity for storage.
  • Example 1 AF configures events to UDM/PCF via NEF
  • FIG. 5a a schematic diagram of a process for configuring a subscription terminal event to a UDM/PCF through an NEF is illustrated in the following example.
  • the method may include the following steps:
  • the AF determines to subscribe to the “end of the terminal after the DDN fails” event to the network side.
  • the AF sends a first message to the NEF, the first message being used to subscribe to the terminal event.
  • the message can be Nnef_EventExposure_subscribe.
  • the subscription message includes the following information: service description information, terminal identifier (or group identifier), AF identifier, event type information, and DNN/S-NSSAI/AF-Service-Id.
  • the NEF processes the message, including checking, according to the local policy, whether the AF is authorized to perform the service request, whether the message has a problem, whether the AF request exceeds a quota, or exceeds a request frequency. If the check passes, the NEF stores the following information: service description information, terminal identity (or group identity), event type information, and DNN/S-NSSAI/AF-Service-Id. And the NEF allocates an event correlation identifier (for example, NEF reference ID) of the terminal event. The event correlation identifier is used to identify an association relationship between a terminal event and a functional entity that subscribes to the terminal event. Event type information is used to identify terminal events.
  • the NEF may also store the following information: an AF identifier or an AF address. The AF can be found by the AF logo or the AF address, and the message can be sent to the AF.
  • the NEF sends a second message to the UDM/PCF, where the second message is used to subscribe to the terminal event.
  • the message can be Nudm_EventExposure_subscribe/Npcf_EventExposure_subscribe.
  • the subscription message includes the following information: service description information, terminal identifier (or may be a group identifier), event type information, event association identifier, and DNN/S-NSSAI/AF-Service-Id.
  • the subscription message may further include an AF identifier or an AF address.
  • the event type information is determined according to event type information provided by the AF, and may be the same event type or a new event type generated for an event supporting the AF subscription.
  • the NEF may send a message to the UDM and the PCF, respectively.
  • the message sent to the UDM may include a terminal identifier (or may be a group identifier), an event type information, and an event association identifier.
  • the message sent to the PCF includes a terminal identifier (or may be a group identifier), event type information, an event association identifier, service description information, and DNN/S-NSSAI/AF-Service-Id.
  • the event type information is determined according to the event type information provided by the AF, and may be the same event type or a new event type generated by an event for supporting the AF subscription.
  • the NEF may map the AF-Service-Id to the DNN/S-NSSAI, and the stored information is DNN/S-NSSAI.
  • the UDM/PCF checks whether the message is valid, including checking whether the network supports event monitoring, whether the request is in the receiving range, and the like. When the check is passed, the UDM/PCF stores the service description information, the terminal identifier (or group identifier), the AF identifier, the event type information, the event association identifier, and the DNN/S-NSSAI/AF-Service-Id.
  • the information stored by the UDM is a terminal identifier (or a group identifier), an AF identifier, an event type information, and an event association identifier; and the PCF stores the service description information and the terminal identifier (or Group ID), AF ID, event type information, event correlation ID, and DNN/S-NSSAI.
  • the UDM may map the AF-Service-Id to the DNN/S-NSSAI, and the stored information is DNN/S-NSSAI.
  • the UDM/PCF may send a third message to the UDR, where the third message is used to subscribe to the terminal event.
  • the message can be Nudr_EventExposure_subscribe.
  • the UDR stores the above information for subscribing to the terminal event.
  • Example 2 AF configures events to UDR through PCF
  • FIG. 5b a schematic diagram of a method for configuring a subscription terminal event to a UDR through a PCF is shown in FIG. 5b.
  • the method may include the following steps:
  • the AF determines to subscribe to the “end of the terminal after the DDN fails” event to the network side.
  • the AF sends a first message to the PCF, the first message being used to subscribe to the terminal event.
  • the message can be Npcf_EventExposure_subscribe.
  • the subscription message includes the following information: service description information, terminal identifier (or group identifier), AF identifier, event type information, and DNN/S-NSSAI/AF-Service-Id.
  • the PCF processes the message, including, according to the local policy, checking whether the AF authorizes execution of the service request, whether the message has a problem, whether the AF request exceeds a quota, or exceeds a request frequency. If the check passes, the PCF stores the following information: service description information, terminal identification (or group identification), event type information, and DNN/S-NSSAI/AF-Service-Id. And assign an event correlation identifier corresponding to the terminal event (for example, PCF reference ID). The event correlation identifier is used to identify an association relationship between a terminal event and a functional entity that subscribes to the terminal event. Event type information is used to identify terminal events.
  • the subscription message may further include an AF identifier or an AF address.
  • the PCF sends a second message to the UDR, where the second message is used to subscribe to the terminal event.
  • the message can be Nudr_EventExposure_subscribe).
  • the message includes the following information: service description information, terminal identity or group identity, event type information, PCF reference ID, and DNN/S-NSSAI/AF-Service-Id.
  • the subscription message may also include an AF identity or an AF address.
  • whether the UDR check message is valid includes checking whether the network supports event monitoring, whether the request is in a receiving range, and the like.
  • the UDR stores the following information: service description information, terminal identifier or group identifier, event type information, PCF reference ID, and DNN/S-NSSAI/AF-Service-Id.
  • the UDR can also store the AF logo or AF address.
  • Example 3 AF configures events to UDR through NEF
  • FIG. 5c a schematic diagram of a process for subscribing a terminal event to a UDR through an NEF is illustrated in the following example.
  • the method may include the following steps:
  • the AF determines to subscribe to the “end of the terminal after the DDN fails” event to the network side.
  • the AF sends a first message to the NEF, the first message being used to subscribe to the terminal event.
  • the message can be Nnef_EventExposure_subscribe.
  • the message includes the following information: service description information, terminal identity or group identity, AF identity, event type information, and DNN/S-NSSAI/AF-Service-Id.
  • the NEF processes the message, including, according to the local policy, checking whether the AF is authorized to perform the service request, whether the message has a problem, whether the AF request exceeds a quota, or exceeds a request frequency. If the check passes, the NEF stores the following information: service description information, terminal identifier or group identifier, event type information, and DNN/S-NSSAI/AF-Service-Id. And assign an event correlation identifier for the terminal event (for example, NEF reference ID). The event correlation identifier is used to identify an association relationship between a terminal event and a functional entity that subscribes to the terminal event. Event type information is used to identify terminal events.
  • the NEF can also store the AF logo or AF address.
  • the NEF sends a second message to the UDR, where the second message is used to subscribe to the terminal event.
  • the message can be Nudr_EventExposure_subscribe.
  • the message includes the following information: service description information, terminal identifier or group identifier, event type information, NEF reference ID, and DNN/S-NSSAI/AF-Service-Id.
  • the message may also include an AF identity or an AF address.
  • the event type information is determined according to event type information provided by the AF, and may be the same event type or a new event type generated for an event supporting the AF subscription. Further, the NEF may generate multiple events according to the event information sent by the AF, and store the data in the UDR.
  • the UDR checks whether the message is valid, including checking whether the network supports event monitoring, whether the request is in the receiving range, and the like.
  • the UDR stores the following information: service description information, terminal identifier (or group identifier), event type information, NEF reference ID, and DNN/S-NSSAI/AF-Service-Id.
  • the UDR can also store the AF logo or AF address.
  • an application function entity configures a method for subscribing to a terminal event to a network. If a service needs to subscribe to a terminal event, the application function entity subscribes the terminal event to the control function entity in the 5G network, specifically When the service is executed, the control function entity subscribes the terminal event to the specific session management function entity, thereby implementing subscription and monitoring of the terminal event in the 5G architecture.
  • FIG. 6 is a schematic flowchart of a communication method according to an embodiment of the present disclosure, where the method may include the following steps:
  • the control function entity determines the session management function entity according to at least one of a data network name, a slice information, and an application function service identifier.
  • control function entity determines the session management function entity according to at least one of the data network name, the slice information, and the application function service identifier, and may be the control function entity according to the data network name, or according to the slice information, or according to the application function service identifier,
  • the session management function entity is determined either according to the data network name and the slice information, or according to the data network name and the application function service identifier, or according to the handover information and the application function service identifier, or according to the data network name, the slice information, and the application function service identifier.
  • the control function entity sends a first message to the session management function entity.
  • the first message is used to subscribe to a terminal event, and the first message includes service description information, where the service description information is used to indicate a service corresponding to the terminal event.
  • the session management function entity sends a second message to the user plane function entity.
  • the second message is used to indicate that the user plane function entity performs service detection.
  • the service is a service corresponding to the subscribed terminal event.
  • the second message may be a service information request, and the user plane function entity is instructed to report the service information.
  • S504 is not required.
  • the service information may be at least one of a source IP address, a source port number, and an index information, and the index information is used to index to a specific event.
  • the downlink data packet may be a dropped downlink data packet.
  • the session management function entity sends a service information request to the user function entity.
  • the user plane function entity detects the service.
  • the user plane function entity sends a service detection notification to the session management function entity.
  • the service detection notification is used to indicate the occurrence of business data.
  • the session management function entity receives the service detection notification.
  • the service detection notification may be service information, that is, service information in S503, and the service information is determined according to the downlink data packet. Specifically, it is determined according to the header of the received downlink packet. For example, when the downlink data packet is an IP data packet, its header contains IP quintuple information; when the downstream data packet is an Ethernet data packet, its header contains a MAC address.
  • the session management function entity sends a notification for monitoring the terminal event to the access and mobility management function entity in response to the service detection notification.
  • the notification of monitoring the terminal event may include event association information, such as an event association identifier (NEF Reference ID).
  • the event association information is used to determine event reporting information.
  • the session management function entity sends event association information to the mobility management entity according to the service description information and the service information, that is, by comparing the service information and the service description information, and when the service information and the service description information match, the mobility is performed.
  • the management entity sends event association information.
  • the access and mobility management function entity monitors the subscribed terminal event.
  • the access and mobility management function entity detects the terminal event, send a terminal event notification to a functional entity that subscribes to the terminal event.
  • the terminal event notification includes at least one of the following: an identifier of the terminal corresponding to the terminal event and an event association identifier of the terminal event, where the event association identifier is used to identify an association relationship between the terminal event and a functional entity that subscribes to the terminal event.
  • the functional entity subscribing to the terminal event receives the terminal event notification.
  • This embodiment still takes 5G as an example.
  • the subscription of the terminal event is configured to the control function entity.
  • the control function entity or the UDR saves the identifier of the terminal corresponding to the terminal event, the event type information of the terminal event, the DNN, the slice information, the application function service identifier, the service description information, and the event association identifier.
  • the control function entity receives the association request sent by the SMF, and the association request is used to request event subscription for the service corresponding to the session.
  • the request may include DNN, slice information, or AF-service-ID.
  • the control function entity obtains the DNN of the terminal event configured in the foregoing configuration process from the local or UDR.
  • the control function entity determines that the DNN included in the session service is consistent with the DNN of the terminal event configured in the foregoing configuration process, or the control function entity obtains the slice information of the terminal event configured in the foregoing configuration process from the local or UDR, and determines the session service usage.
  • the slice information is consistent with the slice information configured in the foregoing configuration flow (if the request includes an AF-service-ID, the AF-service-ID may also be used to derive the DNN and the slice information), and the control function entity determines the SMF that sends the association request. And then send a first message to the SMF, the first message being used to subscribe to the terminal event.
  • control function entity receives the terminal event of the AF subscription, and determines the session with the corresponding DNN and the slice information.
  • the control function entity determines the SMF of the session associated with the DNN and the slice information, and may also actively send a first message to the SMF for subscribing to the terminal event.
  • the first message includes service description information, where the service description information is used to indicate a service corresponding to the terminal event, and may also be used to determine an application function entity that provides a service for the terminal.
  • the first message may further include an event association identifier and event type information of the terminal event.
  • the event association identifier is used to identify an association relationship between the terminal event and the functional entity that subscribes to the terminal event, and the event type information is used to identify the terminal event.
  • the event association identifier may be a reference ID generated by the control function entity in the foregoing configuration process.
  • the reference ID is associated with the AF ID.
  • the terminal event may be an event that requires various types of status or information to be acquired from the network, and the event type of the terminal event may also be a defined type of terminal event.
  • the event type of the terminal event includes a terminal available notification event after the DDN fails, a terminal reachable event, and the like.
  • the event type can also be represented by the event ID.
  • the event ID indicates the type of event being subscribed to, such as availability after DDN failure.
  • the SMF receives the first message. And send a second message to the UPF.
  • the second message is used to instruct the UPF to perform service detection.
  • the service is the service corresponding to the subscribed terminal event, that is, the service corresponding to the service description information.
  • the second message may be that the SMF sends a corresponding rule to the UPF, and the service data is detected according to the rule.
  • the UPF receives the downlink data sent by the data network, and detects the service corresponding to the subscribed terminal event according to a packet detection rule (PDR), such as a packet filter, or an indicator.
  • PDR packet detection rule
  • the packet detection rule includes service description information, such as an IP triplet.
  • the rule may be that when the access network tunnel information of the session is not stored in the UPF, the user plane tunnel needs to be established to send the downlink data to the terminal, and the UPF sends a service detection notification to the SMF.
  • the service detection notification is used to indicate the occurrence of business data.
  • the service data is service data corresponding to the service description information.
  • the service description information may be represented by event filter information.
  • Event filter information is used to determine the conditions that match the notification event.
  • the event filter information includes event parameter types and event parameter values (s).
  • the event parameter type may be service description information.
  • the event parameter value can be specific service description information, such as IP triplet, Application ID.
  • the SMF receives the service detection notification. And in response to the service detection notification. A notification to monitor the terminal event is sent to the AMF.
  • the AMF detects the status of the terminal.
  • the terminal event is a terminal available notification event after the DDN fails
  • the AMF or the SMF detects that the terminal is in an unavailable state
  • the terminal event is activated to monitor the subscribed terminal event.
  • the terminal is in an unavailable state, that is, the network initiates paging for the terminal, but does not receive a response, or the terminal is in PSM mode, or the terminal is in the MICO mode.
  • the AMF When the AMF detects that the terminal is connected to the network, for example, the terminal initiates a tracking area update (TAU) request or a service request, the AMF sends a terminal event notification to the functional entity subscribing to the terminal event.
  • the terminal event notification includes at least one of the following: an identifier of the terminal corresponding to the terminal event and an event association identifier of the terminal event, where the event association identifier is used to identify an association relationship between the terminal event and a functional entity that subscribes to the terminal event.
  • the functional entity subscribing to the terminal event receives the terminal event notification.
  • the AF that subscribes to the terminal event can be distinguished according to the identifier of the terminal in the event notification of the terminal; if multiple AFs subscribe to multiple terminal events to the same terminal, According to the event association identifier in the terminal event notification, the AF that subscribes to the terminal event can be distinguished; if multiple AFs subscribe to multiple terminal events to multiple terminals, the identifier can be distinguished according to the identifier of the terminal and the event association identifier in the terminal event notification. Subscribe to the AF of the terminal event. Therefore, the service service can be provided to the terminal by one or more application function entities. When the terminal event is subscribed, the service corresponding to the terminal event is indicated by the service description information, so that the application function entity that subscribes to the terminal event can be distinguished.
  • the functional entity that subscribes to the terminal event may be an SMF, an AF, or an NEF.
  • the AF may resend the downlink data to the terminal after receiving the terminal event notification (notifying the terminal).
  • the event reporting information may be used to identify the reported event information. In this embodiment, it can be used to describe the presence after the DMF failure event reported by the AMF or the SMF.
  • FIG. 6 is a schematic flowchart of a communication method according to an embodiment of the present disclosure, where the method may include the following steps:
  • control function entity determines the session management function entity according to at least one of a data network name, a slice information, and an application function service identifier.
  • control function entity determines the session management function entity according to at least one of the data network name, the slice information, and the application function service identifier, and may be the control function entity according to the data network name, or according to the slice information, or according to the application function service identifier,
  • the session management function entity is determined either according to the data network name and the slice information, or according to the data network name and the application function service identifier, or according to the handover information and the application function service identifier, or according to the data network name, the slice information, and the application function service identifier.
  • the control function entity sends a first message to the session management function entity.
  • the first message is used to subscribe to a terminal event, and the first message includes service description information, where the service description information is used to indicate a service corresponding to the terminal event.
  • the session management function entity sends a second message to the user plane function entity.
  • the second message is used to indicate that the user plane function entity performs service detection.
  • the service is a service corresponding to the subscribed terminal event.
  • the second message may be a service information request, indicating that the user plane function entity reports the service information.
  • S504' is not required.
  • the service information may be a source IP address of the downlink data packet, at least one of the source port numbers, or an index information, and the index information is used to index to a specific event.
  • the downlink data packet may be a dropped downlink data packet.
  • the session management function entity sends a service information request to the user function entity.
  • the user plane function entity detects the service.
  • the user plane function entity sends a service detection notification to the session management function entity.
  • the service detection notification is used to indicate the occurrence of business data.
  • the session management function entity receives the service detection notification.
  • the service detection notification may be service information, i.e., service information in S503', the service information being determined according to the downlink data packet. Specifically, it is determined according to the header of the received downlink packet. For example, when the downlink data packet is an IP data packet, its header contains IP quintuple information; when the downstream data packet is an Ethernet data packet, its header contains a MAC address.
  • the session management function entity sends a terminal service occurrence notification to the network open function entity in response to the service detection notification.
  • the session management entity receives a subscription to control the terminal event of the functional entity. After receiving the service detection notification sent by the user plane function entity, and determining that the terminal is unreachable, the session management function entity sends a terminal service occurrence notification to the NEF.
  • the terminal event notification includes at least one of the following: an identifier of the terminal corresponding to the terminal event and an event association identifier of the terminal event, where the event association identifier is used to identify an association relationship between the terminal event and a functional entity that subscribes to the terminal event.
  • the functional entity subscribing to the terminal event receives the terminal event notification.
  • the NEF Since the NEF receives the terminal service occurrence notification of the SMF, the NEF sends a terminal event notification to the AF when the NEF receives the terminal reachability notification sent by the AMF.
  • the SMF receives the subscription of the terminal event, and notifies the NEF when the terminal is unreachable, and sends a terminal event notification to the AF when the NEF receives the terminal reachability notification sent by the AMF.
  • the subscription and notification of terminal events for specific services are implemented under the 5G architecture.
  • FIG. 6c is a schematic flowchart of a specific example NEF performing terminal event notification. among them:
  • UDM/PCF determines the target SMF according to the DNN/S-NSSAI/AF-service-ID, and subscribes to the terminal events to the SMF and the AMF.
  • the DNN/S-NSSAI/AF-service-ID may be obtained from the UDR or stored locally.
  • UDM or PCF can subscribe to terminal events to AMF and SMF in the following two ways:
  • Method 1 The UDM or PCF sends event 1 (such as DDN failed UE available event) event association identifier and SMF transmission event 2 (such as service detection event), event association identifier, and service description information to the AMF.
  • event 1 such as DDN failed UE available event
  • SMF transmission event 2 such as service detection event
  • event association identifier such as service description information
  • Method 2 The UDM sends an event 1 (such as a DDN failed UE available event) event association identifier to the AMF, and the PCF sends an event 2 (such as a service detection event), an event association identifier, and a service description information to the SMF.
  • an event 1 such as a DDN failed UE available event
  • an event 2 such as a service detection event
  • an event association identifier such as a service description information
  • UDM/PCF sends a first message to the AMF.
  • UDM/PCF sends a second message (eg, Nsmf_EventExposure) to the target SMF.
  • a second message eg, Nsmf_EventExposure
  • the second message includes service description information, event type information, and event association identifier (for example, NEF reference ID), and may also include information such as NEF ID.
  • the event type is a business detection event.
  • the SMF/AMF receives the first message.
  • the SMF associates the two together.
  • the two are sent together (sent in the same message) to indicate that they are associated, or the service description information is sent in the service detection event subscription message, which is associated with them.
  • the SMF sends a service detection message to the UPF by using an N4 session establishment or modification process.
  • the service detection message includes service description information.
  • the SMF may determine which event is triggered by the data corresponding to the event, and therefore send the event association identifier to the corresponding NEF.
  • the UPF detects the corresponding service according to the service detection message. That is, the service corresponding to the service description information is detected.
  • the service detection message may be a service information request, and the user plane function entity is reported to report the service information.
  • the service information may be a source IP address of the downlink data packet, at least one of the source port numbers, or an index information, and the index information is used to index to a specific event.
  • the downlink data packet may be a dropped downlink data packet.
  • the session management function entity sends a service information request to the user function entity.
  • the AMF sends the UE unreachable information to the SMF.
  • the AMF may send the UE unreachable information to the SMF when receiving the service data sent by the other AF and detecting that the UE is unreachable; or the AMF sends the service data sent by the AF, and sends the data to the SMF when the DDN data fails to be detected.
  • UE unreachable information may be sent to the SMF when receiving the service data sent by the other AF and detecting that the UE is unreachable; or the AMF sends the service data sent by the AF, and sends the data to the SMF when the DDN data fails to be detected.
  • S504" may be any step before S506".
  • the AF sends a downlink data packet to the terminal.
  • the UPF sends a service detection notification to the SMF.
  • the UPF detects that the downlink data packet is a service corresponding to the subscribed terminal event.
  • the UPF When the access tunnel information of the session is not stored in the UPF, a user plane tunnel needs to be established, and the UPF sends a service detection notification to the SMF.
  • the service detection notification is used to indicate the occurrence of the detected service data.
  • the service corresponding to the subscribed terminal event that is, the service corresponding to the service description information.
  • the packet detection rule includes service description information.
  • the service description information is an IP quintuple
  • the UPF detects the received downlink data packet according to the IP quintuple.
  • the downlink packet corresponding to the IP quintuple is detected, it is confirmed that the occurrence of the service data is detected.
  • the service detection notification may be service information, that is, service information in S503", and the service information is determined according to the downlink data packet. Specifically, it is based on the header of the received downlink data packet. For example, when the downlink data packet is an IP data packet, its header contains IP quintuple information; when the downstream data packet is an Ethernet data packet, its header contains a MAC address.
  • SMF sends an event notification to NEF.
  • the SMF notifies the NEF terminal service to occur.
  • the terminal initiates a connection to the network.
  • the terminal initiates a TAU request or a service request to the network.
  • the AMF sends a UE reachable event notification to the NEF.
  • the NEF sends a UE terminal event notification to the AF.
  • an event is sent to the AF according to the record.
  • the UE reachable event is sent to the AF of the recorded service corresponding event.
  • the record is deleted. If it is unreachable, the record is saved, and when the UE reachable event is received, an event is sent to the AF according to the record. For example, the UE is sent to the AF corresponding to the recorded service corresponding event. event.
  • Example 1 AMF receives subscriptions for terminal events from SMF, performs event monitoring and notification
  • FIG. 7a it is a schematic flowchart of an exemplary communication method.
  • the AMF is notified by the SMF to monitor the terminal event.
  • the UDM/PCF performs the following process during the session establishment process or after the session is established:
  • UDM/PCF determines the target SMF according to the DNN/S-NSSAI/AF-service-ID.
  • the DNN/S-NSSAI/AF-service-ID can be obtained from the UDR or stored locally.
  • the UDM/PCF sends a first message (eg, Nsmf_EventExposure) to the target SMF.
  • the first message includes service description information, event type information, and event association identifier (for example, NEF reference ID), and may also include information such as NEF ID.
  • the event type is a terminal available event after the DDN failed.
  • the SMF receives the first message.
  • the SMF associates the two together.
  • the two are sent together (sent in the same message) to indicate that they are associated, or the service description information is sent in the availability after DDN failure event subscription message, which is associated with them.
  • the SMF sends a service detection message to the UPF by using an N4 session establishment or modification process.
  • the service detection message includes service description information.
  • the SMF may determine which event is triggered by the data corresponding to the event, and therefore send the event association identifier to the corresponding AMF.
  • the service detection message may be a service information request, and the user plane function entity is reported to report the service information.
  • S605 is not required.
  • the service information may be a source IP address of the downlink data packet, at least one of the source port numbers, or an index information, and the index information is used to index to a specific event.
  • the downlink data packet may be a dropped downlink data packet.
  • the session management function entity sends a service information request to the user function entity.
  • the UPF detects the corresponding service according to the service detection message. That is, the service corresponding to the service description information is detected.
  • the AF sends a downlink data packet to the terminal.
  • the UPF detects, according to the packet detection rule, that the downlink data packet is a service corresponding to the subscribed terminal event.
  • the UPF When the access tunnel information of the session is not stored in the UPF, a user plane tunnel needs to be established, and the UPF sends a service detection notification to the SMF.
  • the service detection notification is used to indicate the occurrence of the detected service data.
  • the service corresponding to the subscribed terminal event that is, the service corresponding to the service description information.
  • the packet detection rule includes service description information.
  • the service description information is an IP triplet
  • the UPF detects the received downlink data packet according to the IP triplet.
  • the SMF sends a second message (for example, Namf_CommunicationN1N2MessageTransfer) to the AMF in response to the service detection notification sent by the UPF.
  • the second message includes event type information and an event association identifier (for example, a NEF reference ID), and may further include an NEF ID.
  • the NEF ID is used by the AMF to send a notification to the NEF corresponding to the NEF ID.
  • the event type information and the event association identifier may be carried in different messages.
  • the SMF may carry the NEF reference ID in the Namf_CommunicationN1N2MessageTransfer and the event type information in the Namf_EventExposure_Subscribe.
  • the order of the two messages is not in order.
  • the service detection notification may be service information, that is, service information in S603, and the service information is determined according to the downlink data packet. Specifically, it is determined according to the header of the received downlink packet. For example, when the downlink data packet is an IP data packet, its header contains IP quintuple information; when the downstream data packet is an Ethernet data packet, its header contains a MAC address.
  • the AMF detects that the terminal is unavailable, and the AMF sends a response message (for example, Namf_CommunicationN1N2MessageTransfer) to the SMF to notify the DDN that the failure has occurred.
  • a response message for example, Namf_CommunicationN1N2MessageTransfer
  • the SMF further sends a DDN failure indication to the UPF.
  • the AMF determines that the terminal is unavailable, the AMF sets or activates an available event after the DDN fails, and the AMF starts monitoring the availability status of the terminal.
  • the terminal initiates a connection to the network. For example, the terminal initiates a TAU request or a service request to the network.
  • the AMF determines that an event is available after the local setting DDN fails, and sends a terminal event notification (for example, Namf_EventExposure_Notify) to the NEF.
  • the terminal event notification includes at least one of the following information: a terminal identifier and an event association identifier (for example, an NEF reference ID).
  • the NEF sends a terminal event notification (for example, Namf_EventExposure_Notify) to the AF according to the identifier of the terminal and/or the NEF reference ID.
  • a terminal event notification for example, Namf_EventExposure_Notify
  • the AF After receiving the notification of the terminal event, the AF determines that the terminal is available, and can retransmit the downlink data to the terminal.
  • Example 2 SMF performs event monitoring and notification
  • FIG. 7b it is a flow chart of another exemplary communication method.
  • the AMF performs terminal reachable event monitoring, and when the AMF detects that the terminal is reachable, sends a terminal reachable notification to the session management function entity, the notification is used to indicate the SMF.
  • the UDM/PCF performs the following process during the session establishment process or after the session is established:
  • UDM/PCF determines the target SMF according to the DNN/S-NSSAI/AF-service-ID.
  • the DNN/S-NSSAI/AF-service-ID is obtained from the UDR or stored locally.
  • the UDM/PCF sends a first message (eg, Nsmf_EventExposure) to the target SMF.
  • the first message includes service description information, event type information, and event association identifier (for example, NEF reference ID), and may also include information such as NEF ID.
  • the event type is a terminal available event after the DDN failed.
  • the SMF sends a service detection message to the UPF by using an N4 session establishment or modification process.
  • the service detection message is used to instruct the UPF to detect the service corresponding to the subscribed terminal event, that is, the service corresponding to the service description information.
  • the service detection message may be a service information request, and the user plane function entity is instructed to report the service information.
  • S705 is not required.
  • the service information may be a source IP address of the downlink data packet, at least one of the source port numbers, or an index information, and the index information is used to index to a specific event.
  • the downlink data packet can be a dropped downlink data packet.
  • the session management function entity sends a service information request to the user function entity.
  • the AF sends a downlink data packet to the terminal.
  • the UPF determines, according to the packet detection rule, that the downlink data packet is a service corresponding to the subscribed terminal event, and needs to be established.
  • the UPF sends a service detection notification to the SMF.
  • the service detection notification is used to indicate the occurrence of the detected service data.
  • the SMF sends a second message (for example, Namf_CommunicationN1N2MessageTransfer) to the AMF in response to the service detection notification sent by the UPF.
  • the second message is for subscribing to a terminal event, and the second message includes event type information.
  • the event type is a terminal reachable event.
  • the AMF detects that the terminal is unreachable, and sends a response message to the SMF (for example, Namf_CommunicationN1N2MessageTransfer).
  • the response message is used to indicate that the terminal is unreachable.
  • the SMF further sends a DDN failure indication to the UPF.
  • AMF activates the terminal reachable event.
  • the SMF determines that the terminal is unavailable (such as the terminal is in the PSM state or the terminal is in the MICO state, etc.), the SMF sets an event that is available after the DDN fails.
  • the terminal initiates a connection to the network. For example, the terminal initiates a TAU request or a service request to the network.
  • the AMF determines that the SMF subscribes to the terminal reachable report event, and sends a first terminal event notification (for example, Namf_EventExposure_Notify) to the SMF.
  • the first terminal event notification is used to notify the terminal that it is reachable.
  • the SMF determines an event that is available after the DDN fails to be set, and sends a second terminal event notification to the NEF.
  • the second terminal event notification includes at least one of the following information: an identifier of the terminal and an event association identifier of the terminal event.
  • the NEF sends the second terminal event notification to the AF according to the identifier of the terminal and/or the event association identifier.
  • S712b may also be performed, and the SMF may send a second terminal event notification to the AF.
  • the second terminal event notification includes at least one of the following information: an identifier of the AF, an identifier of the terminal, and an event association identifier of the terminal event.
  • the AF After receiving the notification of the terminal event, the AF determines that the terminal is available, and can retransmit the downlink data to the terminal.
  • Example 3 SMF performs service detection, AMF receives subscription of terminal events from UDM/PCF and performs event detection and notification
  • FIG. 7c it is a schematic flowchart of a communication method of still another example. The specific process is described as follows:
  • UDM/PCF determines the target SMF according to the DNN/S-NSSAI/AF-service-ID.
  • the DNN/S-NSSAI/AF-service-ID is obtained from the UDR or stored locally.
  • the UDM/PCF determines the AMF based on the UE identity.
  • the UDM/PCF sends a first message (eg, Nsmf_EventExposure) to the AMF during the terminal registration process or any other time of the registration state.
  • the first message includes event type information and an event association identifier (eg, NEF reference ID), and may also include an NEF ID.
  • the event type is a terminal available event after the DDN failed.
  • the UDM/PCF sends a second message (eg, Nsmf_EventExposure Service Message) to the target SMF during session establishment or after session establishment.
  • the second message includes service description information and an event association identifier (for example, a NEF reference ID).
  • AMF-PCF refers to a PCF associated with AMF, which is used to provide access and mobility related policies and terminal policies to AMF.
  • SMF-PCF refers to a PCF associated with the SMF for providing session-related policies to the SMF.
  • AMF-PCF and SMF-PCF can be the same functional entity or separate functional entities.
  • the SMF sends a service detection message to the UPF by using an N4 session establishment or modification process.
  • the service detection message is used to instruct the UPF to detect the service corresponding to the subscribed terminal event, that is, the service corresponding to the service description information.
  • the service detection message may be a service information request, and the user plane function entity is reported to report the service information.
  • S805 is not required.
  • the service information may be a source IP address of the downlink data packet, at least one of the source port numbers, or an index information, and the index information is used to index to a specific event.
  • the downlink data packet may be a dropped downlink data packet.
  • the session management function entity sends a service information request to the user function entity.
  • the AF sends a downlink data packet to the terminal.
  • the UPF receives the downlink data packet, and determines, according to the packet detection rule, that the downlink data packet is a subscribed terminal event.
  • the UPF sends a downlink data notification to the SMF.
  • the downlink data notification is used to indicate the occurrence of service data.
  • the downlink data notification may be service information, that is, service information in S803, and the service information is determined according to the downlink data packet. Specifically, it is determined according to the header of the received downlink packet. For example, when the downlink data packet is an IP data packet, its header contains IP quintuple information; when the downstream data packet is an Ethernet data packet, its header contains a MAC address.
  • the SMF sends a third message (for example, Namf_CommunicationN1N2MessageTransfer) to the AMF in response to the service detection notification sent by the UPF.
  • the third message includes an NEF reference ID, and may also include an NEF ID.
  • the SMF activates the AMF in the third message to monitor the terminal event.
  • the SMF notifies the AMF to start monitoring the terminal event, and the UDM/PCF has configured the AMF in the first message.
  • Monitor terminal events That is, configuring the monitoring terminal event and the service corresponding to detecting the service description information may be independent processes, and the two may be indicated in different messages.
  • the third message may include event association information, such as an event association identifier.
  • the event association information is used to determine event reporting information.
  • the session management function entity sends event association information to the mobility management entity according to the service description information and the service information, that is, by comparing the service information and the service description information, and when the service information and the service description information match, the mobility is performed.
  • the management entity sends event association information.
  • the event subscription message and the event monitoring notification are sent by different functional entities or separately by the SMF.
  • the AMF first receives the event subscription information for availability after DDN failure, and then the AMF receives the event monitoring notification, which includes the NEF reference ID, so the AMF can associate this monitoring notification with this event.
  • S807 The AMF detects that the terminal is unavailable, the downlink data notification fails, and the AMF sends a response message (for example, Namf_CommunicationN1N2MessageTransfer) to the SMF to notify the DDN that the failure has occurred.
  • a response message for example, Namf_CommunicationN1N2MessageTransfer
  • the SMF further sends a DDN failure indication to the UPF.
  • the AMF determines that the UE is unavailable (such as the UE is in the PSM state or the UE is in the MICO state, etc.), according to the NEF reference ID, the AMF sets or activates the terminal available event after the corresponding DDN fails. S810.
  • the terminal initiates a connection to the network. For example, the terminal initiates a TAU request or a service request to the network.
  • the AMF determines that the terminal available event after the local setting DDN fails, and sends a terminal event notification (for example, Namf_EventExposure_Notify) to the NEF.
  • the terminal event notification includes at least one of the following information: an identifier of the terminal and an NEF reference ID.
  • AMF there are two main AMF association methods for one or more AF subscription terminal events: (1) AMF only subscribes for an availability after DDN failure for one UE, and then this event can have different NEF Reference. ID, so AMF can report this event to different AFs through NEF, which is a way. (2) Another way is that each AF serving the UE can subscribe to the AMF for this availability after DDN failure event for each event, such that each availability after DDN failure event may correspond to a different AF.
  • AMF can also report this event directly to AF.
  • the NEF sends a terminal event notification (for example, Namf_EventExposure_Notify) to the AF according to the identifier of the terminal and/or the event association identifier.
  • a terminal event notification for example, Namf_EventExposure_Notify
  • the AF After receiving the notification of the terminal event, the AF determines that the terminal is available, and can retransmit the downlink data to the terminal.
  • a terminal event is subscribed to the session management function entity, and the session management function entity notifies the access and the mobile when receiving the service detection notification of the user plane function entity.
  • the sexual management function entity monitors terminal events so that in the 5G architecture, terminal events can be subscribed and monitored for specific services.
  • Example 4 V-SMF performs event monitoring and notification in a roaming scenario
  • FIG. 7d it is a schematic flowchart of a communication method of still another example.
  • the local session management function entity H-SMF
  • V-SMF roaming session management function entity
  • the UDM/PCF performs the following process during the session establishment process or after the session is established:
  • UDM/PCF determines the target H-SMF based on the DNN/S-NSSAI/AF-service-ID.
  • the DNN/S-NSSAI/AF-service-ID is obtained from the UDR or stored locally.
  • UDM/PCF sends a first message (e.g., Nsmf_EventExposure) to the target H-SMF.
  • the first message includes service description information, event type information, and event association identifier (for example, NEF reference ID), and may also include information such as NEF ID.
  • the event type is a terminal available event after the DDN failed.
  • the H-SMF sends the first message to the V-SMF.
  • S703' and the V-SMF send a service detection message to the roaming user plane function entity (V-UPF) through an N4 session establishment or modification procedure.
  • the service detection message is used to instruct the V-UPF to detect the service corresponding to the subscribed terminal event, that is, the service corresponding to the service description information.
  • the service detection message may be a service information request, and the user plane function entity is instructed to report the service information.
  • S705' is not required.
  • the service information may be a source IP address of the downlink data packet, at least one of the source port numbers, or an index information, and the index information is used to index to a specific event.
  • the downlink data packet may be a dropped downlink data packet.
  • the session management function entity sends a service information request to the user function entity.
  • the AF sends a downlink packet to the terminal.
  • the V-UPF determines, according to the packet detection rule, that the downlink data packet is a service corresponding to the subscribed terminal event, When a user plane tunnel needs to be established, the V-UPF sends a service detection notification to the V-SMF.
  • the service detection notification is used to indicate the occurrence of detected business data.
  • the service detection notification may be service information, that is, service information in S703', which is determined according to the downlink data packet. Specifically, it is determined according to the header of the received downlink packet. For example, when the downlink data packet is an IP data packet, its header contains IP quintuple information; when the downstream data packet is an Ethernet data packet, its header contains a MAC address.
  • the V-SMF sends a second message (for example, Namf_CommunicationN1N2MessageTransfer) to the AMF in response to the service detection notification sent by the V-UPF.
  • the second message is for subscribing to a terminal event, and the second message includes event type information.
  • the event type is a terminal reachable event.
  • the second message may include event association information, such as an event association identifier.
  • the event association information is used to determine event reporting information.
  • the session management function entity sends event association information to the mobility management entity according to the service description information and the service information, that is, by comparing the service information and the service description information, and when the service information and the service description information match, the mobility is performed.
  • the management entity sends event association information.
  • the AMF detects that the terminal is unreachable, and sends a response message to the V-SMF (for example, Namf_CommunicationN1N2MessageTransfer).
  • the response message is used to indicate that the terminal is unreachable.
  • the V-SMF further sends a DDN failure indication to the V-UPF.
  • AMF activates the terminal reachable event.
  • the V-SMF determines that the terminal is unavailable (such as the terminal is in the PSM state or the terminal is in the MICO state, etc.), the V-SMF sets an event available after the DDN fails.
  • the terminal initiates a connection to the network. For example, the terminal initiates a TAU request or a service request to the network.
  • the AMF determines that the V-SMF subscribes to the terminal reachable reporting event, and sends a first terminal event notification (for example, Namf_EventExposure_Notify) to the V-SMF.
  • the first terminal event notification is used to notify the terminal that it is reachable.
  • the S712a' and V-SMF determine an event available after setting the DDN failure, and send a second terminal event notification to the NEF.
  • the second terminal event notification includes at least one of the following information: an identifier of the terminal and an event association identifier of the terminal event.
  • the NEF sends the second terminal event notification to the AF according to the identifier of the terminal and/or the event association identifier.
  • S712b' may also be executed, and the V-SMF may send a second terminal event notification to the AF.
  • the second terminal event notification includes at least one of the following information: an identifier of the AF, an identifier of the terminal, and an event association identifier of the terminal event.
  • the AF After receiving the notification of the terminal event, the AF determines that the terminal is available, and can retransmit the downlink data to the terminal.
  • Example 5 In a roaming scenario, the V-SMF performs service detection, and the AMF receives subscriptions of terminal events from the UDM/PCF and performs event detection and notification.
  • FIG. 7e it is a schematic flowchart of a communication method of still another example. The specific process is described as follows:
  • UDM/PCF determines the target H-SMF based on the DNN/S-NSSAI/AF-service-ID.
  • the DNN/S-NSSAI/AF-service-ID is obtained from the UDR or stored locally.
  • the UDM/PCF determines the AMF based on the UE identity.
  • the UDM/PCF (AMF-PCF) sends a first message (e.g., Nsmf_EventExposure) to the AMF.
  • the first message includes event type information and an event association identifier (eg, NEF reference ID), and may also include an NEF ID.
  • the event type is a terminal available event after the DDN failed.
  • the UDM/PCF sends a second message (e.g., Nsmf_EventExposure Service Message) to the target H-SMF.
  • the second message includes service description information and an event association identifier (for example, an NEF reference ID).
  • AMF-PCF refers to a PCF associated with AMF, which is used to provide access and mobility related policies and terminal policies to AMF.
  • SMF-PCF refers to a PCF associated with the H-SMF for providing session-related policies to the H-SMF.
  • AMF-PCF and SMF-PCF can be the same functional entity or separate functional entities.
  • the H-SMF sends a third message to the V-SMF.
  • the third message includes service description information and an event association identifier.
  • the service detection message is used to instruct the V-UPF to detect the service corresponding to the subscribed terminal event, that is, the service corresponding to the service description information.
  • the service detection message may be a service information request, and the user plane function entity is instructed to report the service information.
  • S805' is not required.
  • the service information may be a source IP address of the downlink data packet, at least one of the source port numbers, or an index information, and the index information is used to index to a specific event.
  • the downlink data packet may be a dropped downlink data packet.
  • the session management function entity sends a service information request to the user function entity.
  • the AF sends a downlink packet to the terminal.
  • the V-UPF receives the downlink data packet, and determines, according to the packet detection rule, the downlink data packet is the subscribed terminal.
  • the V-UPF sends a downlink data notification to the V-SMF when the service corresponding to the event needs to establish a user plane tunnel.
  • the downlink data notification is used to indicate the occurrence of service data.
  • the V-SMF sends a fourth message (for example, Namf_CommunicationN1N2MessageTransfer) to the AMF in response to the service detection notification sent by the V-UPF.
  • the fourth message includes an NEF reference ID, and may also include an NEF ID.
  • the V-SMF activates the AMF in the fourth message to monitor the terminal event.
  • the V-SMF notifies the AMF to start monitoring the terminal event, and the UDM/PCF is already in the first
  • the AMF is configured to monitor terminal events. That is, configuring the monitoring terminal event and the service corresponding to detecting the service description information may be independent processes, and the two may be indicated in different messages.
  • the event subscription message and the event monitoring notification are sent by different functional entities or by V-SMF respectively.
  • the AMF first receives the event subscription information for availability after DDN failure, and then the AMF receives the event monitoring notification, which includes the NEF reference ID, so the AMF can associate this monitoring notification with this event.
  • the service detection notification may be service information, i.e., service information in S803', the service information being determined according to the downlink data packet. Specifically, it is determined according to the header of the received downlink packet. For example, when the downlink data packet is an IP data packet, its header contains IP quintuple information; when the downstream data packet is an Ethernet data packet, its header contains a MAC address.
  • the fourth message may include event association information, such as an event association identifier (NEF Reference ID).
  • the event association information is used to determine event reporting information.
  • the session management function entity sends event association information to the mobility management entity according to the service description information and the service information, that is, by comparing the service information and the service description information, and when the service information and the service description information match, the mobility is performed.
  • the management entity sends event association information.
  • AMF detects that the terminal is unavailable, the downlink data notification fails, and the AMF sends a response message (for example, Namf_CommunicationN1N2MessageTransfer) to the V-SMF to notify the DDN that the failure has occurred.
  • a response message for example, Namf_CommunicationN1N2MessageTransfer
  • V-SMF further sends a DDN failure indication to the V-UPF.
  • the AMF determines that the UE is unavailable (such as the UE is in the PSM state or the UE is in the MICO state, etc.), according to the NEF reference ID, the AMF sets or activates the terminal available event after the corresponding DDN fails.
  • the terminal initiates a connection to the network.
  • the terminal initiates a TAU request or a service request to the network.
  • the AMF determines that the terminal available event after the local setting DDN fails, and sends a terminal event notification (for example, Namf_EventExposure_Notify) to the NEF.
  • the terminal event notification includes at least one of the following information: an identifier of the terminal and an NEF reference ID.
  • AMF there are two main AMF association methods for one or more AF subscription terminal events: (1) AMF only subscribes for an availability after DDN failure for one UE, and then this event can have different NEF Reference. ID, so AMF can report this event to different AFs through NEF, which is a way. (2) Another way is that each AF serving the UE can subscribe to the AMF for this availability after DDN failure event for each event, such that each availability after DDN failure event may correspond to a different AF.
  • AMF can also report this event directly to AF.
  • the NEF sends a terminal event notification (for example, Namf_EventExposure_Notify) to the AF according to the identifier of the terminal and/or the event association identifier.
  • a terminal event notification for example, Namf_EventExposure_Notify
  • the AF After receiving the notification of the terminal event, the AF determines that the terminal is available, and can retransmit the downlink data to the terminal.
  • a terminal event is subscribed to the session management function entity, and the session management function entity notifies the access and the mobile when receiving the service detection notification of the user plane function entity.
  • the sexual management function entity monitors terminal events so that in the 5G architecture, terminal events can be subscribed and monitored for specific services.
  • FIG. 8 is a schematic diagram of a module of a communication device according to an embodiment of the present disclosure.
  • the communication device may be a control function entity described in the foregoing communication system, and may be a UDM, a PCF, or an NEF.
  • the communication device 1000 may include: a processing unit 11 and a transmitting unit 12; wherein:
  • the processing unit 11 is configured to determine, according to at least one of a data network name, a slice information, and an application function service identifier, a session management function entity;
  • the sending unit 12 is configured to send a first message to the session management function entity, where the first message is used to subscribe to a terminal event, and the first message includes service description information, where the service description information is used to indicate The service corresponding to the terminal event.
  • the service description information is further used to determine an application function entity that provides a service for the terminal.
  • the first message further includes an event association identifier and event type information of the terminal event, where the event association identifier is used to identify the terminal event and a functional entity that subscribes to the terminal event
  • the association type information is used to identify the terminal event.
  • the sending unit is further configured to send a second message to the access and mobility management function entity, where the second message is used to subscribe to the terminal event, and the second message includes the An event correlation identifier and event type information of the terminal event, where the event association identifier is used to identify an association relationship between the terminal event and a functional entity that subscribes to the terminal event, where the event type information is used to identify the terminal event.
  • the communication device 1000 may further include a receiving unit 13;
  • the receiving unit 13 is configured to receive a third message from an application function entity, where the third message is used to subscribe to the terminal event, and the third message includes the service description information.
  • the third message further includes at least one of the following: an identifier of the terminal corresponding to the terminal event, event type information of the terminal event, the data network name, the slice information, and the The application function service identifier.
  • the receiving unit 13 is further configured to receive the third message that is forwarded by the network open function entity.
  • the sending unit 12 is further configured to send the service description information, the event association identifier, the identifier of the terminal, an event type of the terminal event, the data network name, and a location At least one of the slice information and the application function service identifier is described to the consolidated database function entity for storage.
  • the processing unit 11 is further configured to acquire the service description information, the event association identifier, the identifier of the terminal, and event type information of the terminal event from a local or unified database function entity. At least one of the data network name, the slice information, and the application function service identifier.
  • the receiving unit 13 is further configured to receive the terminal event notification from an access and mobility management function entity or the session management function entity, and the sending unit 11 is further configured to: Sending the terminal event notification to the application function entity.
  • the event type of the terminal event includes a terminal available event after the downlink data notification fails.
  • FIG. 9 is a schematic block diagram of another communication apparatus according to an embodiment of the present application.
  • the communication apparatus may be an access and mobility management function entity described in the foregoing communication system.
  • the communication device 2000a may include a receiving unit 21a, a monitoring unit 22a, and a transmitting unit 23a; wherein:
  • the receiving unit 21a is configured to receive a first message sent by the session management function entity, where the first message is used to subscribe to a terminal event;
  • the monitoring unit 22a is configured to monitor the terminal event that is subscribed to;
  • the sending unit 23a is configured to: when the monitoring unit detects the terminal event, send the terminal event notification to a functional entity that subscribes to the terminal event, where the terminal event notification includes at least one of the following information: An identifier of the terminal corresponding to the terminal event and an event association identifier of the terminal event, where the event association identifier is used to identify an association relationship between the terminal event and a functional entity that subscribes to the terminal event.
  • FIG. 9b is a schematic diagram of still another module of a communication device according to an embodiment of the present application.
  • the communication device may be an access and mobility management function entity described in the foregoing communication system.
  • the communication device 2000b may include a receiving unit 21b, a monitoring unit 22b, and a transmitting unit 23b; wherein:
  • the receiving unit 21b is configured to receive a notification that the session management function entity sends a monitoring terminal reachable event
  • the monitoring unit 22b is configured to monitor the terminal reachable event
  • the sending unit 23b is configured to: when the terminal reachable event is detected, send a terminal reachability notification to the session management function entity, where the terminal reachable notification is used for monitoring the terminal available event after the downlink data notification fails.
  • FIG. 10 is a schematic diagram of still another module of a communication device according to an embodiment of the present disclosure.
  • the communication device may be a session management function entity described in the foregoing communication system.
  • the communication device 3000 may include: a transmitting unit 31 and a receiving unit 32; wherein:
  • the sending unit 31 is configured to instruct the user plane function entity to perform service detection, where the service is a service corresponding to the subscribed terminal event, or is used to send a service information request to the user plane function entity, and the receiving unit 32 is configured to receive the a service detection notification sent by the user plane function entity, or service information, where the service detection notification is used to indicate the occurrence of the service data; and the sending unit 31 is further configured to respond to the service detection notification to access and The mobility management function entity sends a notification to monitor the terminal event.
  • the receiving unit 32 is further configured to receive a first message sent by the control function entity, where the first message is used to indicate the service, and the first message includes service description information of the service. .
  • the first message is further used to subscribe to the terminal event, where the first message includes an event association identifier and event type information of the terminal event, and the event association identifier is used to identify the And an association relationship between the terminal event and a functional entity that subscribes to the terminal event, where the event type information is used to identify the terminal event.
  • the sending unit 31 is configured to instruct the user plane function entity to perform service detection when the access network tunnel information for transmitting the service data is not stored.
  • the terminal event includes a terminal available event after the downlink data notification fails, and the receiving unit 32 is further configured to receive the terminal reachability notification or the downlink data notification sent by the access and mobility management function entity. After the failure, the terminal can notify the event; and after the failure to send the downlink data notification, the terminal can notify the network open function entity or the application function entity.
  • FIG. 11 is a schematic diagram of still another module of a communication device according to an embodiment of the present application.
  • the communication device may be a user plane function entity described in the foregoing communication system.
  • the communication device 4000 may include: a receiving unit 41, a detecting unit 42, and a transmitting unit 43; wherein:
  • the receiving unit 41 is configured to receive a first message or a service information request sent by the session management function entity, where the first message is used to indicate that the service is detected, and the service is a service corresponding to the subscribed terminal event; the detecting unit 42, And the sending unit 43 is configured to send a service detection notification or service information to the session management function entity, where the service detection notification is used to indicate the occurrence of the service data. .
  • the detecting unit 42 is configured to detect, according to the first message, the service when the access network tunnel information for transmitting the service data is not stored.
  • FIG. 12 is a schematic structural diagram of hardware of a communication apparatus according to an embodiment of the present application.
  • the communication device includes a processor and may also include a receiver, a transmitter, and a memory.
  • the receiver, transmitter, memory and processor are interconnected by a bus.
  • the memory includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read only memory (EPROM), or a portable A compact disc read-only memory (CD-ROM) for use in related instructions and data.
  • RAM random access memory
  • ROM read-only memory
  • EPROM erasable programmable read only memory
  • CD-ROM portable A compact disc read-only memory
  • the receiver is for receiving data and/or signals
  • the transmitter is for transmitting data and/or signals.
  • the transmitter and receiver can be separate devices or a single device.
  • the processor may include one or more processors, for example, including one or more central processing units (CPUs).
  • CPUs central processing units
  • the CPU may be a single-core CPU or may be Multi-core CPU.
  • the memory is used to store program code and data of the network device.
  • the processor is configured to invoke program code and data in the memory to perform the steps in the above method embodiments.
  • the processor is configured to invoke program code and data in the memory to perform the steps in the above method embodiments.
  • Figure 12 only shows a simplified design of the communication device.
  • the communication device may also include other necessary components, including but not limited to any number of transceivers, processors, controllers, memories, etc., and all communication devices that can implement the embodiments of the present invention are in the present invention. Within the scope of protection.
  • the communication device can be a control function entity in the communication system described above.
  • the related functions implemented by the receiving unit 13 in FIG. 8 may be implemented by a receiver, and related functions implemented by the transmitting unit 12 may be implemented by a transmitter, and related functions implemented by the processing unit 11 may pass through one or more processors. to realise.
  • the processor is configured to determine a session management function entity according to at least one of a data network name, a slice information, and an application function service identifier;
  • the transmitter is configured to send a first message to the session management function entity, where the first message is used to subscribe to a terminal event, and the first message includes service description information, where the service description information is used to indicate the The service corresponding to the terminal event.
  • the service description information is further used to determine an application function entity that provides a service for the terminal.
  • the first message further includes an event association identifier and event type information of the terminal event, where the event association identifier is used to identify the terminal event and a functional entity that subscribes to the terminal event
  • the association type information is used to identify the terminal event.
  • the transmitter is further configured to send a second message to the access and mobility management function entity, the second message is used to subscribe to the terminal event, and the second message includes the terminal
  • the event association identifier of the event and the event type information the event association identifier is used to identify an association relationship between the terminal event and a functional entity that subscribes to the terminal event, and the event type information is used to identify the terminal event.
  • the receiver is configured to receive a third message from an application function entity, the third message is used to subscribe to the terminal event, and the third message includes the service description information.
  • the third message further includes at least one of the following: an identifier of the terminal corresponding to the terminal event, event type information of the terminal event, the data network name, the slice information, and the The application function service identifier.
  • the receiver is further configured to receive the third message forwarded by a network open function entity.
  • the transmitter is further configured to send the service description information, the event association identifier, an identifier of the terminal, an event type of the terminal event, the data network name, the slice At least one of the information and the application function service identifier to the consolidated database function entity for storage.
  • the processor is further configured to acquire, from a local or unified database function entity, the service description information, the event association identifier, the identifier of the terminal, event type information of the terminal event, At least one of a data network name, the slice information, and the application function service identifier.
  • the receiver is further configured to receive the terminal event notification from an access and mobility management function entity or the session management function entity; and the sending unit 11 is further configured to send a The terminal event notification is notified to the application function entity.
  • the event type of the terminal event includes a terminal available event after the downlink data notification fails.
  • the communication device can be an access and mobility management function entity in the communication system described above.
  • the related functions implemented by the monitoring unit 22a in FIG. 9a may be implemented by one or more processors, the related functions implemented by the transmitting unit 23a may be implemented by a transmitter, and the related functions implemented by the receiving unit 21a may be implemented by the receiver. to realise.
  • the receiver is configured to receive a first message sent by a session management function entity, where the first message is used to subscribe to a terminal event;
  • the processor is configured to monitor the terminal event that is subscribed to;
  • the transmitter is configured to: when the monitoring unit detects the terminal event, send the terminal event notification to a functional entity that subscribes to the terminal event, where the terminal event notification includes at least one of the following information: the terminal An identifier of the terminal corresponding to the event and an event association identifier of the terminal event, where the event association identifier is used to identify an association relationship between the terminal event and a functional entity that subscribes to the terminal event.
  • the communication device can be an access and mobility management functional entity in the communication system described above.
  • the related functions implemented by the receiving unit 21b in FIG. 9b may be implemented by a receiver, and related functions implemented by the monitoring unit 22b may be implemented by one or more processors, and related functions implemented by the transmitting unit 23b may be implemented by the transmitter. to realise.
  • the receiver is configured to receive a notification that the session management function entity sends a monitoring terminal reachable event
  • the processor is configured to monitor a terminal reachable event
  • the transmitter is configured to send a terminal reachability notification to the session management function entity when the terminal reachable event is detected, and the terminal reachability notification is used for monitoring the terminal available event after the downlink data notification fails.
  • the communication device can be a session management function entity in the communication system described above.
  • the related functions implemented by the transmitting unit 31 in FIG. 10 can be implemented by a transmitter, and the related functions implemented by the receiving unit 32 can be implemented by a receiver.
  • the transmitter is configured to instruct the user plane function entity to perform service detection, where the service is a service corresponding to the subscribed terminal event;
  • the receiver is configured to receive a service detection notification sent by the user plane function entity, where the service detection notification is used to indicate the occurrence of the service data;
  • the transmitter is further configured to send a notification to the access and mobility management function entity to monitor the terminal event in response to the traffic detection notification.
  • the receiver is further configured to receive a first message sent by the control function entity, where the first message is used to indicate the service, and the first message includes service description information of the service.
  • the first message is further used to subscribe to the terminal event, where the first message includes an event association identifier and event type information of the terminal event, and the event association identifier is used to identify the And an association relationship between the terminal event and a functional entity that subscribes to the terminal event, where the event type information is used to identify the terminal event.
  • the transmitter is configured to instruct the user plane function entity to perform service detection when the access network tunnel information for transmitting the service data is not stored.
  • the terminal event includes a terminal available event after the downlink data notification fails
  • the receiver is further configured to: after receiving the terminal reachability notification or the downlink data notification sent by the access and mobility management function entity, The terminal may use the event notification; and the terminal may notify the network to open the functional entity or the application functional entity after the downlink data notification fails.
  • the communication device can be a user plane functional entity in the communication system described above.
  • the related functions implemented by the receiving unit 41 in FIG. 11 may be implemented by a receiver, and related functions implemented by the detecting unit 42 may be implemented by one or more processors, and related functions implemented by the transmitting unit 43 may be implemented by the transmitter. to realise.
  • the receiver is configured to receive a first message sent by the session management function entity, where the first message is used to indicate that the service is detected, and the service is a service corresponding to the subscribed terminal event;
  • the processor is configured to detect the service according to the first message
  • the transmitter is configured to send a service detection notification to the session management function entity, where the service detection notification is used to indicate the occurrence of the service data.
  • the processor is configured to detect the service according to the first message when the access network tunnel information for transmitting the service data is not stored.
  • the communication device can be a session management function entity in the communication system described above.
  • the related functions implemented by the receiving unit 52 in FIG. 15 may be implemented by a receiver, and related functions implemented by the indicating unit 51 and the monitoring unit 53 may be implemented by one or more processors, and related functions implemented by the transmitting unit 54 It can be implemented by a transmitter.
  • the processor is configured to instruct a user plane function entity to perform service detection, where the service is a service corresponding to a terminal event subscribed by the first application function entity;
  • the receiver is configured to receive a service detection notification sent by the user plane function entity, where the service detection notification is used to indicate that the data of the service is detected;
  • the processor is further configured to: when the terminal is unreachable, monitor the terminal event according to the service detection notification;
  • the transmitter is configured to send a terminal event notification to the network open function entity or the first application function entity when the terminal event is detected.
  • FIG. 13 is a schematic flowchart diagram of still another communication method according to an embodiment of the present disclosure, where the method may include the following steps:
  • the control function entity determines the session management function entity according to at least one of a data network name, a slice information, and an application function service identifier.
  • control function entity determines the session management function entity according to at least one of the data network name, the slice information, and the application function service identifier, and may be the control function entity according to the data network name, or according to the slice information, or according to the application function service identifier,
  • the session management function entity is determined either according to the data network name and the slice information, or according to the data network name and the application function service identifier, or according to the handover information and the application function service identifier, or according to the data network name, the slice information, and the application function service identifier.
  • the control function entity sends a first message to the session management function entity.
  • the first message is used to subscribe to a terminal event, and the first message includes service description information, where the service description information is used to indicate a service corresponding to the terminal event.
  • the terminal event includes a terminal available event or a terminal reachable event after the downlink data notification fails.
  • the subscription terminal event is used to monitor the UE reachability event or the transmit data available event when the UE is unreachable or fails to send the service data when the service data is sent, so that the AF resends the service data.
  • the session management function entity sends a second message to the user plane function entity.
  • the second message is used to indicate that the user plane function entity performs service detection.
  • the service is a service corresponding to the subscribed terminal event.
  • the second message may be a service information request, and the user plane function entity is instructed to report the service information.
  • the S904 is not required.
  • the service information may be a source IP address of the downlink data packet, at least one of the source port numbers, or an index information, and the index information is used to index to a specific event.
  • the downlink data packet may be a dropped downlink data packet.
  • the session management function entity sends a service information request to the user function entity.
  • the SMF instructs the UPF to perform service detection by sending a second message.
  • the user plane function entity detects the service.
  • the user plane function entity sends a service detection notification to the session management function entity.
  • the service detection notification is used to indicate the occurrence of business data.
  • the session management function entity receives the service detection notification.
  • the service detection notification may be service information, that is, service information in S903, and the service information is determined according to the downlink data packet. Specifically, it is determined according to the header of the received downlink packet. For example, when the downlink data packet is an IP data packet, its header contains IP quintuple information; when the downstream data packet is an Ethernet data packet, its header contains a MAC address.
  • the session management function entity monitors the terminal event according to the service detection notification.
  • receiving the access and the mobility management function entity when receiving the downlink data transmission failure notification sent by the access and mobility management function entity, or when detecting the service data of the second application function entity, receiving the access and the mobility management function entity sends the unreachable The notification determines that the terminal is unreachable.
  • the SMF monitors the terminal event according to the service detection notification, which means that the SMF monitors the terminal event after receiving the service detection notification and the UE is unreachable.
  • the session management function entity sends a terminal event notification to the application function entity.
  • the method for monitoring the event of the terminal is to receive the terminal reachable event notification sent by the access and mobility management function entity or the terminal available event notification of the downlink data transmission failure.
  • the terminal event is detected when receiving the terminal reachability event notification or the downlink data transmission failure terminal available event notification sent by the access and mobility management function entity.
  • the terminal event notification is sent to the NEF or the first application function entity.
  • the session management function entity instructs the user plane function entity to detect a specific service, and when the terminal is unreachable, monitors the terminal event according to the service detection notification sent by the user plane function entity, and monitors When the terminal event is sent, the terminal event notification is sent, so that the terminal event can be subscribed and notified for the specific service under the 5G architecture.
  • FIG. 13 The embodiment shown in FIG. 13 will be described in detail below with reference to specific examples:
  • FIG. 14 is a schematic flowchart of still another communication method according to an embodiment of the present application, where the method may include the following steps:
  • UDM/PCF determines the target SMF according to the DNN/S-NSSAI/AF-service-ID.
  • the DNN/S-NSSAI/AF-service-ID may be obtained from the UDR or stored locally.
  • the UDM/PCF sends a first message (eg, Nsmf_EventExposure) to the target SMF.
  • the first message includes service description information, event type information, and event association identifier (for example, NEF reference ID), and may also include information such as NEF ID.
  • the event type is a terminal available event after the DDN failed.
  • the SMF receives the first message.
  • the SMF associates the two together.
  • the two are sent together (sent in the same message) to indicate that they are associated, or the service description information is sent in the availability after DDN failure event subscription message, which is associated with them.
  • the SMF sends a service detection message to the UPF through an N4 session establishment or modification process.
  • the service detection message includes service description information.
  • the SMF may determine which event is triggered by the data corresponding to the event, and therefore send the event association identifier to the corresponding AMF.
  • the service detection message may be a service information request, and the user plane function entity is reported to report the service information.
  • S1006 is not required.
  • the service information may be a source IP address of the downlink data packet, at least one of the source port numbers, or an index information, and the index information is used to index to a specific event.
  • the downlink data packet may be a dropped downlink data packet.
  • the session management function entity sends a service information request to the user function entity.
  • the UPF detects the corresponding service according to the service detection message. That is, the service corresponding to the service description information is detected.
  • the AMF sends the UE unreachable information to the SMF.
  • the AMF may send the UE unreachable information to the SMF when receiving the service data sent by the other AF and detecting that the UE is unreachable; or the AMF sends the UE unreachable information to the SMF when the DDN data fails.
  • S1004 may be any step before S1007.
  • S1005 The AF sends a downlink data packet to the terminal.
  • the UPF detects, according to the packet detection rule, that the downlink data packet is a service corresponding to the subscribed terminal event.
  • the UPF When the access tunnel information of the session is not stored in the UPF, a user plane tunnel needs to be established, and the UPF sends a service detection notification to the SMF.
  • the service detection notification is used to indicate the occurrence of the detected service data.
  • the service corresponding to the subscribed terminal event that is, the service corresponding to the service description information.
  • the packet detection rule includes service description information.
  • the service description information is an IP triplet
  • the UPF detects the received downlink data packet according to the IP triplet.
  • the SMF activates an event when the UE is unreachable.
  • the terminal is reachable by the SMF.
  • the terminal initiates a connection to the network.
  • the terminal initiates a TAU request or a service request to the network.
  • the AMF sends a UE reachable event notification to the SMF.
  • the service detection notification may be service information, that is, service information in S1003, and the service information is determined according to the downlink data packet. Specifically, it is determined according to the header of the received downlink packet. For example, when the downlink data packet is an IP data packet, its header contains IP quintuple information; when the downstream data packet is an Ethernet data packet, its header contains a MAC address.
  • the SMF determines to locally set the UE reachable event, and sends a terminal event notification to the NEF.
  • the terminal event notification includes at least one of the following information: a terminal identifier and an event association identifier (for example, an NEF reference ID).
  • the NEF sends a terminal available event notification (for example, Namf_EventExposure_Notify) to the AF according to the identifier of the terminal and/or the NEF reference ID.
  • a terminal available event notification for example, Namf_EventExposure_Notify
  • the AF After receiving the notification of the terminal event, the AF determines that the terminal is available, and can retransmit the downlink data to the terminal.
  • FIG. 14 is a schematic flowchart of still another communication method according to an embodiment of the present application, where the method may include the following steps:
  • UDM/PCF determines the target SMF according to the DNN/S-NSSAI/AF-service-ID.
  • the DNN/S-NSSAI/AF-service-ID can be obtained from the UDR or stored locally.
  • the UDM/PCF sends a first message to the target SMF.
  • S1103 The SMF sends a service detection message to the UPF through an N4 session establishment or modification process.
  • S1104 The AF sends a downlink data packet to the terminal.
  • S1105 The UPF sends a service detection notification to the SMF.
  • S1106 The SMF sends a second message to the AMF.
  • the second message here is a normal DDN message, not an event subscription message.
  • the second message may be a service information request, indicating that the user plane function entity reports the service information.
  • the service information may be a source IP address of the downlink data packet, at least one of the source port numbers, or an index information, and the index information is used to index to a specific event.
  • the downlink data packet may be a dropped downlink data packet.
  • the session management function entity sends a service information request to the user function entity.
  • the AMF sends a response message to the SMF to notify the UE that it is unreachable.
  • the AMF after receiving the second message, notifies the SMF UE that it is unreachable if it detects that the UE is unreachable.
  • S1108 The SMF activates an event when the UE is unreachable.
  • the SMF sends a downlink data notification failure message to the UPF.
  • the AMF stores a first indication, where the first indication is used to indicate that the SMF is notified that the UE is unreachable.
  • the AMF stores the record to notify the SMF when the UE is reachable.
  • S1111 The terminal initiates a connection to the network.
  • the AMF sends a UE reachability event notification to the SMF.
  • the SMF determines to locally set the UE reachable event, and sends a terminal event notification to the NEF.
  • the NEF sends a terminal available event notification to the AF according to the identifier of the terminal and/or the NEF reference ID.
  • the AF After receiving the notification of the terminal event, the AF determines that the terminal is available, and can retransmit the downlink data to the terminal.
  • FIG. 14 is a schematic flowchart of still another communication method according to an embodiment of the present application. This method is applied to roaming scenarios. The method can include the following steps:
  • UDM/PCF determines to subscribe to the terminal event to the SMF.
  • the UDM/PCF determines the target H-SMF based on the DNN/S-NSSAI/AF-service-ID.
  • the DNN/S-NSSAI/AF-service-ID can be obtained from the UDR or stored locally.
  • UDM/PCF sends a first message (eg, Nsmf_EventExposure) to the target H-SMF.
  • the first message includes service description information, event type information, and event association identifier (for example, NEF reference ID), and may also include information such as NEF ID.
  • the event type is a terminal available event after the DDN failed.
  • the H-SMF receives the first message.
  • the V-SMF After the V-SMF receives the availability after DDN failure event and the service description information, the V-SMF associates the two together.
  • the two are sent together (sent in the same message) to indicate that they are associated, or the service description information is sent in the availability after DDN failure event subscription message, which is associated with them.
  • the V-SMF sends a service detection message to the V-UPF through an N4 session establishment or modification process.
  • the service detection message includes service description information.
  • the V-SMF may determine which event is triggered by the data corresponding to the event, and therefore send the event association identifier to the corresponding AMF.
  • the V-UPF detects the corresponding service according to the service detection message. That is, the service corresponding to the service description information is detected.
  • the second message may be a service information request, and the user plane function entity is instructed to report the service information.
  • the S1205 is not required.
  • the service information may be a source IP address of the downlink data packet, at least one of the source port numbers, or an index information, and the index information is used to index to a specific event.
  • the downlink data packet may be a dropped downlink data packet.
  • the session management function entity sends a service information request to the user function entity.
  • S1204 The AF sends a downlink data packet to the terminal.
  • the V-UPF detects, according to the packet detection rule, that the downlink data packet is a service corresponding to the subscribed terminal event.
  • the V-UPF When the access tunnel information of the session is not stored in the V-UPF, a user plane tunnel needs to be established, and the V-UPF sends a service detection notification to the V-SMF.
  • the service detection notification is used to indicate the occurrence of the detected service data.
  • the V-SMF may use a notification event after the DDN fails to activate the UE when the UE is unreachable.
  • the terminal event is monitored by the V-SMF.
  • the terminal initiates a connection to the network.
  • the AMF sends a first terminal event notification to the V-SMF.
  • the first terminal event notification is a UE reachable event notification.
  • S1208a and the V-SMF determine that the UE reachable event is set locally, and then send a terminal event notification to the NEF.
  • the NEF sends a terminal available event notification (for example, Namf_EventExposure_Notify) to the AF according to the identifier of the terminal and/or the NEF reference ID.
  • a terminal available event notification for example, Namf_EventExposure_Notify
  • the V-SMF sends a terminal available event notification to the AF.
  • the AF After receiving the notification of the terminal event, the AF determines that the terminal is available, and can retransmit the downlink data to the terminal.
  • FIG. 14 is a schematic flowchart of still another communication method according to an embodiment of the present application. This method is applied to roaming scenarios. The method can include the following steps:
  • UDM/PCF determines to subscribe to the terminal event to the SMF.
  • the UDM/PCF determines the target H-SMF based on the DNN/S-NSSAI/AF-service-ID.
  • the DNN/S-NSSAI/AF-service-ID can be obtained from the UDR or stored locally.
  • UDM/PCF sends a first message (eg, Nsmf_EventExposure) to the target H-SMF.
  • the first message includes service description information, event type information, and event association identifier (for example, NEF reference ID), and may also include information such as NEF ID.
  • the event type is a terminal available event after the DDN failed.
  • the H-SMF receives the first message.
  • the H-SMF After the H-SMF receives the availability after DDN failure event and the service description information, the H-SMF associates the two together.
  • the two are sent together (sent in the same message) to indicate that they are associated, or the service description information is sent in the availability after DDN failure event subscription message, which is associated with them.
  • the H-SMF sends a service detection message to the H-UPF through an N4 session establishment or modification process.
  • the service detection message includes service description information.
  • the H-SMF may determine which event is triggered by the data corresponding to the event, and therefore send the event association identifier to the corresponding AMF.
  • the H-UPF detects the corresponding service according to the service detection message. That is, the service corresponding to the service description information is detected.
  • the second message may be a service information request, and the user plane function entity is instructed to report the service information.
  • S1306 is not required.
  • the service information may be a source IP address of the downlink data packet, at least one of the source port numbers, or an index information, and the index information is used to index to a specific event.
  • the downlink data packet may be a dropped downlink data packet.
  • the session management function entity sends a service information request to the user function entity.
  • the H-SMF receives the UE unreachable information.
  • the AMF may send the UE unreachable information to the H-SMF when receiving the service data sent by other AFs and detecting that the UE is unreachable.
  • S1304 may be any step before S1307.
  • S1305 The AF sends a downlink data packet to the terminal.
  • the H-UPF detects, according to the packet detection rule, that the downlink data packet is a service corresponding to the subscribed terminal event.
  • the H-UPF When the access tunnel information of the session is not stored in the H-UPF, a user plane tunnel needs to be established, and the H-UPF sends a service detection notification to the H-SMF.
  • the service detection notification is used to indicate the occurrence of the detected service data.
  • the H-SMF may use a notification event after the DDN fails to be activated when the UE is unreachable.
  • the terminal event is monitored by the H-SMF.
  • the terminal initiates a connection to the network.
  • the S1308 and AMF send a terminal event notification to the V-SMF.
  • the terminal event notification is a UE reachable event notification.
  • S1309b and the H-SMF determine that the UE reachable event is set locally, and then send a terminal event notification to the NEF.
  • the NEF sends a terminal available event notification (for example, Namf_EventExposure_Notify) to the AF according to the identifier of the terminal and/or the NEF reference ID.
  • a terminal available event notification for example, Namf_EventExposure_Notify
  • the AF After receiving the notification of the terminal event, the AF determines that the terminal is available, and can retransmit the downlink data to the terminal.
  • FIG. 14 e is a schematic flowchart of still another communication method provided by an embodiment of the present application, where the method may include the following steps:
  • the S1400.V-SMF receives event information or indication information from the H-SMF.
  • the indication information is used to instruct the V-SMF to send an N4 session release request to the V-UPF when receiving the session deactivation information sent by the AMF.
  • the UE performs a connection release procedure with the (R) AN.
  • the (R)AN sends a UE context release request to the AMF.
  • the AMF sends a UE context release command to the (R) AN.
  • the (R)AN completes the connection release procedure with the UE.
  • the (R)AN sends a UE context release complete message to the AMF.
  • the AMF sends a Session Update Session Context (PDU session_update SM contex) message to the V-SMF.
  • PDU session_update SM contex Session Update Session Context
  • the V-SMF deletes the N4 session of the V-UPF based on the indication information, and notifies the H-SMF to modify the N4 session of the A-UPF.
  • the V-SMF obtains event monitoring information, and the session can be managed based on the event monitoring information.
  • V-SMF sends a N4 session release request to the V-UPF.
  • S1406'a.V-SMF sends a session update request (PDU session update request) to the H-SMF.
  • V-UPF sends a N4 session release response to the V-SMF.
  • the H-SMF sends a PDU session update response to the V-SMF.
  • the V-SMF sends a PDU session update SM context ACK to the AMF.
  • the A-UPF manages an intermediate user plane functional entity (I-UPF).
  • the method can include the following steps:
  • the UE performs a connection release procedure with the (R) AN.
  • the (R)AN sends a UE context release request to the AMF.
  • the AMF sends a UE context release command to the (R) AN.
  • the (R)AN completes the connection release procedure with the UE.
  • the (R)AN sends a UE context release complete message to the AMF.
  • the AMF sends a Session Update Session Context (PDU session_update SM contex) message to the SMF.
  • PDU session_update SM contex Session Update Session Context
  • the SMF deletes the N4 session of the I-UPF based on the event monitoring information, and modifies the N4 session of the A-UPF.
  • the SMF obtains event monitoring information, and the session can be managed based on the event monitoring information.
  • the N4 session is a session corresponding to the service description information.
  • the S1506a.SMF sends a N4 session release request to the I-UPF.
  • the SMF sends a N4 session modification request to the A-UPF.
  • S1506b.I-UPF sends a N4 session release response to the SMF.
  • S1506'b.A-UPF sends a N4 session modification response to the SMF.
  • the SMF sends a PDU session update SM context ACK to the AMF.
  • FIG. 15 is a schematic structural diagram of still another communication apparatus according to an embodiment of the present disclosure.
  • the apparatus 5000 may include:
  • the instructing unit 51 is configured to instruct the user plane function entity to perform service detection, where the service is a service corresponding to the terminal event subscribed by the first application function entity.
  • the receiving unit 52 is configured to receive a service detection notification sent by the user plane function entity, where the service detection notification is used to indicate that the data of the service is detected.
  • the monitoring unit 53 is configured to monitor the terminal event according to the service detection notification when the terminal is unreachable.
  • the sending unit 54 is configured to send a terminal event notification to the network open function entity or the first application function entity when the terminal event is detected.
  • the terminal event includes a terminal available event or a terminal reachable event after the downlink data notification fails.
  • the monitoring the terminal event is to receive a terminal reachable event notification or a downlink data sending failure terminal available event notification sent by the access and mobility management function entity.
  • the apparatus further includes: a determining unit, configured to receive a downlink data transmission failure notification sent by the access and mobility management function entity, or when detecting the second application function entity When the service data is received, the unreachable notification sent by the access and mobility management function entity is received, and then the terminal is determined to be unreachable.
  • the receiving unit 52 is further configured to receive a first message sent by a local session management function entity, where the first message is used to indicate the service and subscribe to the terminal event,
  • the first message includes service description information of the service, an event association identifier of the terminal event, and event type information, where the event association identifier is used to identify an association between the terminal event and a functional entity that subscribes to the terminal event.
  • the relationship, the event type information is used to identify the terminal event.
  • FIG. 16 is a schematic flowchart of still another communication method according to an embodiment of the present application, where:
  • S1601 The control function entity sends a first message of the terminal event to the AMF.
  • the UDM/PCF determines to subscribe to the AMF event.
  • the UDM/PCF determines to subscribe to the AMF event.
  • the first message is used to subscribe to a terminal event, and the first message includes service description information and DNN/S-NSSAI.
  • the first message may further include an event type, a NEF ID, and an NEF reference ID.
  • the AMF After receiving the first message, the AMF sends a second message to the SMF.
  • the second message is used to subscribe to a service detection event, and the second message includes the service description information.
  • the second message may further include an event type, a NEF ID, a NEF reference ID, or an event type, an AMF ID, and an AMF reference ID.
  • the AMF reference ID is generated by the AMF and is used to associate the corresponding event or event report.
  • the AMF determines whether the established PDU session or the DNN/S-NSSAI of the PDU session being established is the same as the DNN/S-NSSAI included in the first message, and when the same, the AMF sends the second to the SMF. Message.
  • S1602 specifically includes: sending a subscription request to a local session management function entity or a roaming session management function entity; or
  • a session context update request is sent to the local session management function entity or the roaming session management function entity, the session context update request being used to subscribe to the terminal event.
  • the SMF After the SMF receives the second message, the SMF sends a third message to the UPF.
  • the third message is used to indicate that the service is detected, and the service is a service corresponding to the subscribed terminal event.
  • the S1603 includes: sending the third message to the user plane function entity during or after the PDU session deactivation process, where the third message is used to indicate that the service is detected, and the service is a subscribed terminal.
  • the business corresponding to the event.
  • the SMF subscribes to the service detection event to the UPF through an N4 session establishment or modification process or a new N4 message.
  • the third message may be a service information request, indicating that the user plane function entity reports the service information.
  • the S1604 is not required.
  • the service information may be a source IP address of the downlink data packet, at least one of the source port numbers, or an index information, and the index information is used to index to a specific event.
  • the downlink data packet may be a dropped downlink data packet.
  • the session management function entity sends a service information request to the user function entity.
  • the UPF receives the third message, and when the service data is detected, the UPF sends a service detection notification to the SMF.
  • the service detection notification is used to indicate the occurrence of service data.
  • the service detection notification may be service information, that is, service information in S1603, and the service information is determined according to the downlink data packet. Specifically, it is determined according to the header of the received downlink packet. For example, when the downlink data packet is an IP data packet, its header contains IP quintuple information; when the downstream data packet is an Ethernet data packet, its header contains a MAC address.
  • the SMF After the S1605 and the SMF receive the service detection notification, the SMF sends the service detection notification to the AMF.
  • the service detection notification carries a reference ID for indexing to a particular event.
  • the reference ID is generated by AMF or NEF. If NEF is generated, the optional NEF ID is included to prevent different NEFs from generating the same reference ID and cannot uniquely identify a specific event.
  • the notification of monitoring the terminal event may include event association information, such as a NEF Reference ID.
  • the event association information is used to determine event reporting information.
  • the session management function entity sends event association information to the mobility management entity according to the service description information and the service information, that is, by comparing the service information and the service description information, and when the service information and the service description information match, the mobility is performed.
  • the management entity sends event association information.
  • the S1606 and the AMF After receiving the foregoing service detection notification, the S1606 and the AMF detect whether the UE is reachable. When the UE is unreachable, the above terminal event is activated.
  • the control function entity may perform terminal event subscription to the AMF.
  • the AMF receives the service detection notification and detects that the terminal is unreachable, the terminal event is activated.
  • the AMF detects that the terminal is reachable, it sends a terminal event notification to the capability open node or the application function entity, so that the terminal event can be subscribed to the specific service under the 5G architecture.
  • FIG. 17 is a schematic flowchart of still another communication method in the embodiment of the present application, where:
  • the UDM/PCF determines to subscribe to the AMF event.
  • UDM/PCF (AMF-PCF) sends a subscription request message (Namf_EventExposure) to the AMF, including the event type, NEF ID, NEF reference ID, DNN/S-NSSAI, and service description information.
  • AMF sends a Namf_EventExposure response message to the UDM/PCF.
  • the AMF determines to subscribe to the SMF according to the DNN/S-NSSAI, and the AMF determines whether the established PDU session or the DNN/S-NSSAI of the PDU session being established and the DNN/S-NSSAI of the event are the same.
  • the S1704a and the AMF send an Nsmf_EventExposure request to the SMF.
  • the request message includes an event type, a service description, a NEF ID, and an NEF reference ID. Or include event type, business description, AMF ID, AMF reference ID.
  • the AMF reference ID is generated by the AMF and is used to associate the corresponding event or event report.
  • S1704b and SMF send an Nsmf_EventExposure response to the AMF.
  • S1705 The SMF subscribes to the service detection event to the UPF through an N4 session establishment or modification process or a new N4 message.
  • the message may be a service information request, indicating that the user plane function entity reports the service information.
  • S1706 is not required.
  • the service information may be a source IP address of the downlink data packet, at least one of the source port numbers, or an index information, and the index information is used to index to a specific event.
  • the downlink data packet may be a dropped downlink data packet.
  • the session management function entity sends a service information request to the user function entity.
  • the UPF receives the data packet sent by the AF.
  • the service detection report is sent to the SMF.
  • the service detection report may be service information, that is, service information in S1703, and the service information is determined according to the downlink data packet. Specifically, it is determined according to the header of the received downlink packet. For example, when the downlink data packet is an IP data packet, its header contains IP quintuple information; when the downstream data packet is an Ethernet data packet, its header contains a MAC address.
  • the SMF sends Nsmf_EventExposureNotify to the AMF, and the message carries a reference ID for indexing to a specific event.
  • the reference ID is generated by AMF or NEF. If NEF is generated, the optional NEF ID is included to prevent different NEFs from generating the same reference ID and cannot uniquely identify a specific event.
  • the notification of monitoring the terminal event may include event association information, such as an event association identifier (NEF Reference ID).
  • the event association information is used to determine event reporting information.
  • the session management function entity sends event association information to the mobility management entity according to the service description information and the service information, that is, by comparing the service information and the service description information, and when the service information and the service description information match, the mobility is performed.
  • the management entity sends event association information.
  • the UE initiates a connection to the network.
  • S1711 The UE enters the reachable state, and the AMF reports the UE reachable event to the NEF.
  • the NEF further informs the AF that the UE is reachable.
  • FIG. 18 is a schematic flowchart of still another communication method in the embodiment of the present application, where:
  • the UDM/PCF determines to subscribe to the AMF event.
  • UDM/PCF (AMF-PCF) sends a Namf_EventExposure request message to the AMF, including the event type, NEF ID, NEF reference ID, DNN/S-NSSAI, and service description information.
  • the AMF determines to subscribe to the H-SMF according to the DNN/S-NSSAI, and the AMF determines whether the established PDU session or the DNN/S-NSSAI of the PDU session being established and the DNN/S-NSSAI of the event are the same.
  • the S1804a and the AMF send an Nsmf_EventExposure request to the H-SMF.
  • the request message includes an event type, a service description, a NEF ID, and an NEF reference ID. Or include event type, business description, AMF ID, AMF reference ID.
  • the AMF reference ID is generated by the AMF and is used to associate the corresponding event or event report.
  • the subscription request message may be a service information request, and the user plane function entity is reported to report the service information.
  • S1806 is not required.
  • the service information may be a source IP address of the downlink data packet, at least one of the source port numbers, or an index information, and the index information is used to index to a specific event.
  • the downlink data packet may be a dropped downlink data packet.
  • the session management function entity sends a service information request to the user function entity.
  • S1804b and H-SMF send an Nsmf_EventExposure response to the AMF.
  • the AMF subscribes to the H-SMF through the V-SMF.
  • the AMF sends event subscription information to the V-SMF, and the further V-SMF sends event subscription information to the H-SMF.
  • the S1805 and the H-SMF subscribe to the service detection event to the H-UPF through an N4 session establishment or modification process or a new N4 message.
  • the H-UPF receives the data packet sent by the AF.
  • the service detection report is sent to the H-SMF.
  • the service detection report may be service information, that is, service information in S1803, and the service information is determined according to the downlink data packet. Specifically, it is determined according to the header of the received downlink packet. For example, when the downlink data packet is an IP data packet, its header contains IP quintuple information; when the downstream data packet is an Ethernet data packet, its header contains a MAC address.
  • S1808 and H-SMF send Nsmf_EventExposureNotify to the AMF, and the message carries a reference ID for indexing to a specific event.
  • the reference ID is generated by AMF or NEF. If NEF is generated, the optional NEF ID is included to prevent different NEFs from generating the same reference ID and cannot uniquely identify a specific event.
  • the event notification sent by the H-SMF to the V-SMF is sent, so that the V-SMF sends an event notification to the AMF.
  • the notification of monitoring the terminal event may include event association information, such as an event association identifier (NEF Reference ID).
  • the event association information is used to determine event reporting information.
  • the session management function entity sends event association information to the mobility management entity according to the service description information and the service information, that is, by comparing the service information and the service description information, and when the service information and the service description information match, the mobility is performed.
  • the management entity sends event association information.
  • the AMF activates a specific event.
  • the UE initiates a connection to the network.
  • S1811 The UE enters the reachable state, and the AMF reports the UE reachable event to the NEF.
  • the NEF further informs the AF that the UE is reachable.
  • FIG. 19 is a schematic flowchart of still another communication method in the embodiment of the present application, where:
  • UDM/PCF (AMF-PCF) sends a Namf_EventExposure request message to the AMF, including the event type, NEF ID, NEF reference ID, DNN/S-NSSAI, and service description information.
  • AMF sends a Namf_EventExposure response message to the UDM/PCF.
  • the AMF determines to send an event to the SMF according to the DNN/S-NSSAI, and the AMF determines whether the established PDU session or the DNN/S-NSSAI of the PDU session being established and the DNN/S-NSSAI of the event are the same.
  • the S1904a and the AMF send an Nsmf_PDUSession_UpdateSMContext request to the SMF, where the request message includes a service description, a NEF ID, and an NEF reference ID. Or include the service description, AMF ID, AMF reference ID.
  • the AMF reference ID is generated by the AMF and is used to associate the corresponding event or event report.
  • the SMF sends an Nsmf_PDUSession_UpdateSMContext response to the AMF.
  • the SMF sends the service detection information to the UPF through an N4 session establishment or modification process or a new N4 message. Further, the SMF sends the service information to the UPF in the process of deactivating the PDU session, where the UPF is the UPF corresponding to the N3 interface.
  • the subscription request message may be a service information request, indicating that the user plane function entity reports the service information.
  • S1906 is not required.
  • the service information may be a source IP address of the downlink data packet, at least one of the source port numbers, or an index information, and the index information is used to index to a specific event.
  • the downlink data packet may be a dropped downlink data packet.
  • the session management function entity sends a service information request to the user function entity.
  • the UPF receives the data packet sent by the AF.
  • the UPF determines that the specific service is the foregoing, and sends a service notification to the SMF by using the DN message.
  • the service notification may be service information, that is, service information in S1903, and the service information is determined according to the downlink data packet. Specifically, it is determined according to the header of the received downlink packet. For example, when the downlink data packet is an IP data packet, its header contains IP quintuple information; when the downstream data packet is an Ethernet data packet, its header contains a MAC address.
  • the S1908a and the SMF send a Namf_Communication_N1N2Message to the AMF, and the message carries a reference ID for indexing to a specific event.
  • the reference ID is generated by AMF or NEF. If NEF is generated, the optional NEF ID is included to prevent different NEFs from generating the same reference ID and cannot uniquely identify a specific event.
  • the notification of monitoring the terminal event may include event association information, such as an event association identifier (NEF Reference ID).
  • the event association information is used to determine event reporting information.
  • the session management function entity sends event association information to the mobility management entity according to the service description information and the service information, that is, by comparing the service information and the service description information, and when the service information and the service description information match, the mobility is performed.
  • the management entity sends event association information.
  • the AMF activates a specific event.
  • the UE initiates a connection to the network.
  • S1911 The UE enters the reachable state, and the AMF reports the UE reachable event to the NEF.
  • the NEF further informs the AF that the UE is reachable.
  • FIG. 20 is a schematic flowchart of still another communication method in the embodiment of the present application, where:
  • the UDM/PCF determines to subscribe to the AMF event.
  • UDM/PCF (AMF-PCF) sends a Namf_EventExposure request message to the AMF, including the event type, NEF ID, NEF reference ID, DNN/S-NSSAI, and service description information.
  • AMF sends a Namf_EventExposure response message to the UDM/PCF.
  • the AMF determines to send an event to the SMF according to the DNN/S-NSSAI, and the AMF determines whether the established PDU session or the DNN/S-NSSAI of the PDU session being established and the DNN/S-NSSAI of the event are the same.
  • S2004a and AMF send an Nsmf_PDUSession_UpdateSMContext request to the V-SMF, where the request message includes a service description, a NEF ID, and an NEF reference ID. Or include the service description, AMF ID, and AMF reference ID.
  • the AMF reference ID is generated by the AMF and is used to associate the corresponding event or event report.
  • V-SMF sends an Nsmf_PDUSession_UpdateSMContext response to the AMF.
  • the V-SMF sends the service detection information to the UPF through the N4 session establishment or modification process or the new N4 message. Further, the V-SMF sends the service information to the UPF in the process of deactivating the PDU session, where the UPF is the UPF of the N3 interface or the UPF of the N9 interface.
  • the second message may be a service information request, indicating that the user plane function entity reports the service information.
  • the S2006 is not required.
  • the service information may be a source IP address of the downlink data packet, at least one of the source port numbers, or an index information, and the index information is used to index to a specific event.
  • the downlink data packet may be a dropped downlink data packet.
  • the session management function entity sends a service information request to the user function entity.
  • the V-UPF receives the data packet sent by the AF.
  • the service notification is sent to the V-SMF through the DN message.
  • the service notification may be service information, that is, service information in S2003, and the service information is determined according to the downlink data packet. Specifically, it is determined according to the header of the received downlink packet. For example, when the downlink data packet is an IP data packet, its header contains IP quintuple information; when the downstream data packet is an Ethernet data packet, its header contains a MAC address.
  • S2008a and V-SMF send a Namf_Communication_N1N2Message to the AMF, and the message carries a reference ID for indexing to a specific event.
  • the reference ID is generated by AMF or NEF. If NEF is generated, the optional NEF ID is included to prevent different NEFs from generating the same reference ID, and cannot uniquely identify a specific event.
  • the notification of monitoring the terminal event may include event association information, such as an event association identifier (NEF Reference ID).
  • the event association information is used to determine event reporting information.
  • the session management function entity sends event association information to the mobility management entity according to the service description information and the service information, that is, by comparing the service information and the service description information, and when the service information and the service description information match, the mobility is performed.
  • the management entity sends event association information.
  • the AMF activates a specific event.
  • the UE initiates a connection to the network.
  • S2011 The UE enters the reachable state, and the AMF reports the UE reachable event to the NEF.
  • S2012 and NEF further notify the AF that the UE is reachable.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in or transmitted by a computer readable storage medium.
  • the computer instructions may be from a website site, computer, server or data center via a wired (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) Another website site, computer, server, or data center for transmission.
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)). )Wait.
  • the foregoing storage medium includes: a read-only memory (ROM) or a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program code.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种通信方法及装置。该方法包括：根据数据网络名称、切片信息和应用功能服务标识中的至少一个确定会话管理功能实体；向所述会话管理功能实体发送第一消息，所述第一消息用于订阅终端事件，所述第一消息包括业务描述信息，其中，所述业务描述信息用于指示所述终端事件对应的业务。还公开了相应的装置。采用本申请的技术方案，对于管理特定业务的会话管理功能实体，向其订阅终端事件，会话管理功能实体在接收到用户面功能实体的业务检测通知时，通知接入和移动性管理功能实体监测终端事件，从而在5G架构中，可以针对特定的业务进行终端事件的订阅和监测。

Description

通信方法及装置
本申请要求于2018年4月9日提交中国国家知识产权局、申请号为201810313171.8、发明名称为“通信方法及装置”的中国专利申请的优先权，以及要求于2018年11月19日提交中国国家知识产权局、申请号为201811378685.8、发明名称为“通信方法及装置”的中国专利申请的优先权，以及要求于2019年2月18日提交中国国家知识产权局、申请号为201910120722.3、发明名称为“通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
如图1所示的现有的演进分组系统(evolved packet system，EPS)非漫游架构示意图，为了支持安装第三方应用(如机器类型的应用等)的业务能力服务器/应用服务器(service capability server/application server，SCS/AS)使用EPS网络，对现有的网络架构进行了增强。引入了业务能力开放功能(service capability exposure function，)SCEF网元。如图2所示的通过SCEF开放的第三代合作伙伴计划(3rd generation partnership project，3GPP)EPS网络架构中接口的架构示意图，SCEF向SCS/AS提供了安全的3GPP网络接口提供的业务和能力。
机器类型的业务包含一种对时延要求不高的业务，即高延迟业务。基于上述能力开放的架构中，为了支持高延迟业务通信，定义了监测“下行数据通知(downlink data notification，DDN)失败后终端可用通知(availability after DDN failure)”事件。即SCS/AS可以通过SCEF向3GPP EPS网络订阅监测“DDN失败后可用通知”事件。当SCS/AS通过EPS网络向终端发送数据包时，若终端处于不可用状态，EPS网络将激活“DDN失败后可用通知”事件，即监测终端的状态：当终端进入可用状态时，网络通过SCEF向SCS/AS上报终端可用状态，以便SCS/AS重新向终端发送数据。
现有的技术方案中，会话和移动性都是由移动性管理实体(mobility management entity，MME)控制。当接收到服务网关(serving gateway，SGW)发送的DDN消息时，且当终端处于不可用状态时，例如，MME为终端发起寻呼，但是没有收到响应，或者终端处于省电模式(power saving mode，PSM)，或者终端处于只允许终端发起连接(mobile initiated connection only，MICO)模式，MME直接激活监测事件。而在第五代(5 th generation，5G)移动通信系统架构中，会话管理、接入和移动性管理分别由不同的功能实体进行控制。在这种架构中，网络如何配置对应的终端事件并激活上报事件，是目前尚未解决的问题。
发明内容
本申请提供一种通信方法及装置，以实现5G架构下终端事件的订阅。
第一方面，提供了一种通信方法，包括：根据数据网络名称、切片信息和应用功能服 务标识中的至少一个确定会话管理功能实体；以及向所述会话管理功能实体发送第一消息，所述第一消息用于订阅终端事件，所述第一消息包括业务描述信息，其中，所述业务描述信息用于指示所述终端事件对应的业务。
在该方面中，对于管理特定业务的会话管理功能实体，向其订阅终端事件，会话管理功能实体管理终端事件后续的网络配置，从而可以在5G架构下，针对特定的业务进行终端事件的订阅。
结合第一方面，在第一种可能的实现方式中，所述业务描述信息还用于确定为所述终端提供服务的应用功能实体。
在该实现方式中，可以由一个或多个应用功能实体为终端提供业务服务，在订阅终端事件时，通过业务描述信息指示终端事件对应的业务，从而可以区分订阅终端事件的应用功能实体。
结合第一方面或第一方面的第一种可能的实现方式，在第二种可能的实现方式中，所述第一消息还包括所述终端事件的事件关联标识和事件类型信息，所述事件关联标识用于标识所述终端事件和订阅所述终端事件的功能实体之间的关联关系，所述事件类型信息用于标识所述终端事件。
在该实现方式中，在向会话管理功能实体进行终端事件的订阅时，携带事件关联标识和事件类型信息，根据事件关联标识可以识别订阅终端事件的功能实体，根据事件类型信息可以识别终端事件的事件类型。
结合第一方面或第一方面的第一种可能的实现方式，在第三种可能的实现方式中，所述还包括：向接入与移动性管理功能实体发送第二消息，所述第二消息用于订阅所述终端事件，所述第二消息包括所述终端事件的事件关联标识和事件类型信息，所述事件关联标识用于标识所述终端事件和订阅所述终端事件的功能实体之间的关联关系，所述事件类型信息用于标识所述终端事件。
在该实现方式中，在向接入与移动性管理功能实体进行终端事件的订阅时，携带事件关联标识和事件类型信息，根据事件关联标识可以识别订阅终端事件的功能实体，根据事件类型信息可以识别终端事件的事件类型。
结合第一方面或第一方面的第一种可能的实现方式或第一方面的第二种可能的实现方式或第一方面的第三种可能的实现方式，在第四种可能的实现方式中，所述方法还包括：接收来自应用功能实体的第三消息，所述第三消息用于订阅所述终端事件，所述第三消息包括所述业务描述信息。
在该实现方式中，应用功能实体可以向控制功能实体订阅终端事件，在订阅终端事件时，通过业务描述信息指示终端事件对应的业务，从而可以区分订阅终端事件的第三方应用。该控制功能实体可以是网络开放功能实体、统一数据管理功能实体或策略控制功能实体。
结合第一方面的第四种可能的实现方式，在第五种可能的实现方式中，所述第三消息还包括以下至少一个信息：所述终端事件对应的终端的标识、所述终端事件的事件类型信息、所述数据网络名称、所述切片信息和所述应用功能服务标识。
结合第一方面的第四种可能的实现方式或第一方面的第五种可能的实现方式，在第六 种可能的实现方式中，所述接收来自应用功能实体的第三消息，包括：接收经网络开放功能实体转发的所述第三消息。
结合第一方面的第四种可能的实现方式或第一方面的第五种可能的实现方式或第一方面的第六种可能的实现方式，在第七种可能的实现方式中，所述方法还包括：发送所述业务描述信息、所述事件关联标识、所述终端的标识、所述终端事件的事件类型、所述数据网络名称、所述切片信息和所述应用功能服务标识中的至少一个至统一数据库功能实体以便存储。
在该实现方式中，可以由统一数据库功能实体对订阅终端事件的有关信息进行统一存储。
结合第一方面或第一方面的第一种可能的实现方式或第一方面的第二种可能的实现方式或第一方面的第三种可能的实现方式或第一方面的第四种可能的实现方式或第一方面的第五种可能的实现方式或第一方面的第六种可能的实现方式或第一方面的第七种可能的实现方式，在第八种可能的实现方式中，所述方法还包括：从本地或统一数据库功能实体获取所述业务描述信息、所述事件关联标识、所述终端的标识、所述终端事件的事件类型信息、所述数据网络名称、所述切片信息和所述应用功能服务标识中的至少一个。
结合第一方面的第四种可能的实现方式或第一方面的第五种可能的实现方式或第一方面的第六种可能的实现方式或第一方面的第七种可能的实现方式或第一方面的第八种可能的实现方式，在第九种可能的实现方式中，所述方法还包括：接收来自接入和移动性管理功能实体或所述会话管理功能实体的所述终端事件通知；以及发送所述终端事件通知至所述应用功能实体。
在该实现方式中，当监测到终端事件时，由接入和移动性管理功能实体或会话管理功能实体通过网络开放功能实体，然后网络开放功能实体通知应用功能实体监测到该终端事件。
结合第一方面或第一方面的第一种可能的实现方式或第一方面的第二种可能的实现方式或第一方面的第三种可能的实现方式或第一方面的第四种可能的实现方式或第一方面的第五种可能的实现方式或第一方面的第六种可能的实现方式或第一方面的第七种可能的实现方式或第一方面的第八种可能的实现方式或第一方面的第九种可能的实现方式，在第十种可能的实现方式中，所述终端事件的事件类型包括下行数据通知失败后终端可用事件。
相应地，第二方面，提供了一种通信装置，该通信装置具有实现上述方法中通信装置行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
一种可能的实现方式中，所述通信装置包括：处理单元，用于根据数据网络名称、切片信息和应用功能服务标识中的至少一个确定会话管理功能实体；以及发送单元，用于向所述会话管理功能实体发送第一消息，所述第一消息用于订阅终端事件，所述第一消息包括业务描述信息，其中，所述业务描述信息用于指示所述终端事件对应的业务。
另一种可能的实现方式中，所述通信装置包括：处理器，所述处理器用于与存储器耦合，读取并执行所述存储器中的指令，以实现上述方法。
基于同一发明构思，由于该装置解决问题的原理以及有益效果可以参见上述各可能的 通信装置的方法实施方式以及所带来的有益效果，因此该装置的实施可以参见方法的实施，重复之处不再赘述。
第三方面，提供了一种通信方法，包括：接收会话管理功能实体发送的第一消息，所述第一消息用于订阅终端事件；监测被订阅的所述终端事件；以及当监测到所述终端事件时，向订阅所述终端事件的功能实体发送终端事件通知，其中，所述终端事件通知包括以下至少一个信息：所述终端事件对应的终端的标识和所述终端事件的事件关联标识，所述事件关联标识用于标识所述终端事件和订阅所述终端事件的功能实体之间的关联关系。
在该方面中，接入和移动性管理功能实体可以接收会话管理功能实体的终端事件的订阅，在监测到终端事件时，向订阅该终端事件的功能实体发送终端事件通知，从而实现5G架构下终端事件的订阅和监测。
相应地，第四方面，提供了一种通信装置，该通信装置具有实现上述方法中通信装置行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
一种可能的实现方式中，所述通信装置包括：接收单元，用于接收会话管理功能实体发送的第一消息，所述第一消息用于订阅终端事件；监测单元，用于监测被订阅的所述终端事件；以及发送单元，用于当所述监测单元监测到所述终端事件时，向订阅所述终端事件的功能实体发送所述终端事件通知，其中，所述终端事件通知包括以下至少一个信息：所述终端事件对应的终端的标识和所述终端事件的事件关联标识，所述事件关联标识用于标识所述终端事件和订阅所述终端事件的功能实体之间的关联关系。
另一种可能的实现方式中，所述通信装置包括：处理器，所述处理器用于与存储器耦合，读取并执行所述存储器中的指令，以实现上述方法。
基于同一发明构思，由于该装置解决问题的原理以及有益效果可以参见上述各可能的通信装置的方法实施方式以及所带来的有益效果，因此该装置的实施可以参见方法的实施，重复之处不再赘述。
第五方面，提供了一种通信方法，包括：接收会话管理功能实体或者控制功能实体发送的监测终端可达事件的通知；监测终端可达事件；当监测到所述终端可达事件时，向会话管理功能实体或者控制功能实体发送终端可达通知，所述终端可达通知用于下行数据通知失败后终端可用事件的监测。
在该方面中，可由会话管理功能实体进行下行数据通知失败后终端可用事件的监测。接入和移动性管理功能实体在监测到终端可达时，通知会话管理功能实体，从而激活会话管理功能实体进行下行数据通知失败后终端可用事件的监测，从而实现5G架构下终端事件的订阅和监测。
相应地，第六方面，提供了一种通信装置，该通信装置具有实现上述方法中通信装置行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
一种可能的实现方式中，所述通信装置包括：接收单元，用于接收会话管理功能实体发送的监测终端可达事件的通知；监测单元，用于监测终端可达事件；发送单元，用于当所述监测单元监测到所述终端可达事件时，向会话管理功能实体发送终端可达通知，所述 终端可达通知用于下行数据通知失败后终端可用事件的监测。
另一种可能的实现方式中，所述通信装置包括：处理器，所述处理器用于与存储器耦合，读取并执行所述存储器中的指令，以实现上述方法。
基于同一发明构思，由于该装置解决问题的原理以及有益效果可以参见上述各可能的通信装置的方法实施方式以及所带来的有益效果，因此该装置的实施可以参见方法的实施，重复之处不再赘述。
第七方面，提供了一种通信方法，包括：指示用户面功能实体进行业务检测，所述业务为被订阅的终端事件对应的业务；接收所述用户面功能实体发送的业务检测通知，所述业务检测通知用于指示所述业务数据的发生；以及响应于所述业务检测通知，向接入与移动性管理功能实体或者控制功能实体发送监测所述终端事件的通知。
在该方面中，对于管理特定业务的会话管理功能实体，向其订阅终端事件，会话管理功能实体在接收到用户面功能实体的业务检测通知时，通知接入和移动性管理功能实体监测终端事件，从而在5G架构中，可以针对特定的业务进行终端事件的订阅和监测
结合第七方面，在第一种可能的实现方式中，所述指示用户面功能实体进行业务检测，包括：指示所述用户面功能实体在未存储有传输所述业务数据的接入网隧道信息或者下行用户面隧道信息时，进行业务检测；或者指示所述用户面功能实体在未存储有传输所述业务数据的接入网隧道信息或者下行用户面隧道信息时，进行业务检测通知。
结合第七方面或第七方面的第一种可能的实现方式，在第二种可能的实现方式中，所述方法还包括：接收控制功能实体发送的第一消息，所述第一消息用于指示所述业务，所述第一消息包括所述业务的业务描述信息。
在该实现方式中，接收控制功能实体的终端事件的订阅，在订阅终端事件时，通过业务描述信息指示终端事件对应的业务，从而可以区分订阅终端事件的第三方应用。
结合第七方面的第二种可能的实现方式，在第三种可能的实现方式中，所述第一消息还用于订阅所述终端事件，所述第一消息包括所述终端事件的事件关联标识和事件类型信息，所述事件关联标识用于标识所述终端事件和订阅所述终端事件的功能实体之间的关联关系，所述事件类型信息用于标识所述终端事件。
在该实现方式中，在向会话管理功能实体进行终端事件的订阅时，携带事件关联标识和事件类型信息，根据事件关联标识可以识别订阅终端事件的功能实体，根据事件类型信息可以识别终端事件的事件类型。
结合第七方面的第三种可能的实现方式，在第四种可能的实现方式中，所述终端事件包括下行数据通知失败后终端可用事件，所述方法还包括：接收所述接入与移动性管理功能实体发送的终端可达通知或下行数据通知失败后终端可用事件通知；以及发送下行数据通知失败后终端可用通知至网络开放功能实体或应用功能实体。
结合第七方面或第七方面的第一种可能的实现方式，在第五种可能的实现方式中，所述方法还包括：接收本地会话管理功能实体发送的第一消息，所述第一消息用于指示所述业务，所述第一消息包括所述业务的业务描述信息。
在该实现方式中，在漫游场景下，接收本地会话管理功能实体的终端事件的订阅，在订阅终端事件时，通过业务描述信息指示终端事件对应的业务，从而可以区分订阅终端事 件的第三方应用。
相应地，第八方面，提供了一种通信装置，该通信装置具有实现上述方法中通信装置行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
一种可能的实现方式中，所述通信装置包括：发送单元，用于指示用户面功能实体进行业务检测，所述业务为被订阅的终端事件对应的业务；接收单元，用于接收所述用户面功能实体发送的业务检测通知，所述业务检测通知用于指示所述业务数据的发生；以及所述发送单元还用于响应于所述业务检测通知，向接入与移动性管理功能实体发送监测所述终端事件的通知。
另一种可能的实现方式中，所述通信装置包括：处理器，所述处理器用于与存储器耦合，读取并执行所述存储器中的指令，以实现上述方法。
基于同一发明构思，由于该装置解决问题的原理以及有益效果可以参见上述各可能的通信装置的方法实施方式以及所带来的有益效果，因此该装置的实施可以参见方法的实施，重复之处不再赘述。
第九方面，提供了一种通信方法，包括：接收会话管理功能实体发送的第一消息，所述第一消息用于指示进行业务检测，所述业务为被订阅的终端事件对应的业务；根据所述第一消息，检测所述业务；以及发送业务检测通知至所述会话管理功能实体，所述业务检测通知用于指示所述业务数据的发生。
在该方面中，根据会话管理功能实体的业务检测指示，在接收到业务数据时，检测被订阅的终端事件对应的业务，并通知会话管理功能实体，以实现5G架构下终端事件的订阅和监测。
结合第九方面，在第一种可能的实现方式中，所述根据所述第一消息，检测所述业务，包括：根据所述第一消息，当未存储有传输所述业务数据的接入网隧道信息时，检测所述业务。
相应地，第十方面，提供了一种通信装置，该通信装置具有实现上述方法中通信装置行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
一种可能的实现方式中，所述通信装置包括：接收单元，用于接收会话管理功能实体发送的第一消息，所述第一消息用于指示进行业务检测，所述业务为被订阅的终端事件对应的业务；检测单元，用于根据所述第一消息，检测所述业务；以及发送单元，用于发送业务检测通知至所述会话管理功能实体，所述业务检测通知用于指示所述业务数据的发生。
另一种可能的实现方式中，所述通信装置包括：处理器，所述处理器用于与存储器耦合，读取并执行所述存储器中的指令，以实现上述方法。
基于同一发明构思，由于该装置解决问题的原理以及有益效果可以参见上述各可能的通信装置的方法实施方式以及所带来的有益效果，因此该装置的实施可以参见方法的实施，重复之处不再赘述。
第十一方面，提供了一种通信方法，包括：指示用户面功能实体进行业务检测，所述业务为第一应用功能实体订阅的终端事件对应的业务；接收所述用户面功能实体发送的业 务检测通知，所述业务检测通知用于指示检测到所述业务的数据；当终端不可达时，根据所述业务检测通知监测所述终端事件；以及当监测到所述终端事件时，向网络开放功能实体或第一应用功能实体发送终端事件通知。
在该方面中，会话管理功能实体指示用户面功能实体检测特定的业务，在终端不可达时，根据用户面功能实体发送的业务检测通知，监测终端事件，并在监测到终端事件时，发送终端事件通知，从而可以在5G架构下，针对特定的业务进行终端事件的订阅和通知。
结合第十一方面，在第一种可能的实现方式中，所述终端事件包括下行数据通知失败后终端可用事件或终端可达事件。
结合第十一方面的第一种可能的实现方式，在第二种可能的实现方式中，所述监测到所述终端事件为接收所述接入与移动性管理功能实体发送的终端可达事件通知或下行数据发送失败终端可用事件通知。
结合第十一方面或第十一方面的第一种可能的实现方式第十一方面的第二种可能的实现方式，在第三种可能的实现方式中，所述方法还包括：当接收到接入与移动性管理功能实体发送的下行数据发送失败通知，或检测到所述业务之前，接收到接入与移动性管理功能实体发送的不可达通知，则确定所述终端不可达。
在该实现方式中，终端不可达，可以是接收到AMF发送的下行数据失败通知，也可以是其它应用功能实体在发送业务数据时，SMF从AMF接收到不可达通知。
结合第十一方面的第三种可能的实现方式，在第四种可能的实现方式中，所述方法还包括：接收本地会话管理功能实体发送的第一消息，所述第一消息用于指示所述业务和订阅所述终端事件，所述第一消息包括所述业务的业务描述信息，所述终端事件的事件关联标识和事件类型信息，所述事件关联标识用于标识所述终端事件和订阅所述终端事件的功能实体之间的关联关系，所述事件类型信息用于标识所述终端事件。
在该实现方式中，在漫游场景下，可以由访问网络会话管理功能实体进行终端事件的监测。
相应地，第十二方面，提供了一种通信装置，该通信装置具有实现上述第十一方面的方法中通信装置行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
一种可能的实现方式中，所述通信装置包括：指示单元，用于指示用户面功能实体进行业务检测，所述业务为第一应用功能实体订阅的终端事件对应的业务；接收单元，用于接收所述用户面功能实体发送的业务检测通知，所述业务检测通知用于指示检测到所述业务的数据；监测单元，用于当终端不可达时，根据所述业务检测通知监测所述终端事件；以及发送单元，用于当监测到所述终端事件时，向网络开放功能实体或第一应用功能实体发送终端事件通知。
另一种可能的实现方式中，所述通信装置包括：处理器，所述处理器用于与存储器耦合，读取并执行所述存储器中的指令，以实现上述方法。
基于同一发明构思，由于该装置解决问题的原理以及有益效果可以参见上述各可能的通信装置的方法实施方式以及所带来的有益效果，因此该装置的实施可以参见方法的实施，重复之处不再赘述。
第十三方面，提供了一种通信方法，包括：接收控制功能实体发送的终端事件的第一消息，其中，所述第一消息用于订阅终端事件，所述第一消息包括业务描述信息和数据网络名称/单网络切片选择辅助信息DNN/S-NSSAI；向会话管理功能实体发送第二消息，其中，所述第二消息用于订阅业务检测事件，所述第二消息包括所述业务描述信息；接收来自所述会话管理功能实体的业务检测通知；当终端不可达时，激活所述终端事件；以及当检测到所述终端可达时，向能力开放节点或者应用功能实体发送终端可达通知。
在一个实现中，所述向会话管理功能实体发送第二消息，包括：当会话的DNN/S-NSSAI与所述第一消息中包括的DNN/S-NSSAI相同时，向所述会话管理功能实体发送所述第二消息。
在另一个实现中，所述向会话管理功能实体发送第二消息，包括：向本地会话管理功能实体或漫游地会话管理功能实体发送订阅请求；或向本地会话管理功能实体或漫游地会话管理功能实体发送会话上下文更新请求，所述会话上下文更新请求用于订阅所述终端事件。
第十四方面，提供了一种通信方法，包括：接收来自移动性管理功能实体AMF的终端事件的第二消息；向用户面功能实体UPF发送第三消息，所述第三消息用于指示进行业务检测，所述业务为被订阅的终端事件对应的业务；接收来自所述用户面功能实体的业务检测通知，所述业务检测通知用于指示所述业务数据的发生；向所述移动性管理功能实体发送所述业务检测通知。
在一个实现中，所述接收来自移动性管理功能实体的终端事件的第二消息，包括：接收来自所述移动性管理功能实体的会话上下文更新请求，所述会话上下文更新请求用于订阅所述终端事件。
在另一个实现中，向用户面功能实体发送第三消息，包括：在PDU会话去激活过程中或之后，向用户面功能实体发送所述第三消息，所述第三消息用于指示进行业务检测，所述业务为被订阅的终端事件对应的业务。
第十五方面，提供了一种通信方法，包括：接收来自控制功能实体的第一消息，所述第一消息用于订阅终端事件，所述第一消息包括业务描述信息，其中，所述业务描述信息用于指示所述终端事件对应的业务。接收来自用户功能实体UPF的业务信息，所述业务信息为根据下行数据包所确定；以及至少根据所述业务信息，向移动性管理实体或者能力开放实体发送事件关联信息，所述事件关联信息用于确定事件上报信息。
在一个实现中，所述接收用户功能实体的业务信息之前，包括：向用户功能实体发送业务信息请求。
在另一个实现中，所述向用户功能实体发送业务信息请求，包括：若下行数据通知失败，向用户功能实体发送业务信息请求。
在又一个实现中，向移动性管理实体或者能力开放实体发送事件关联信息，所述事件关联信息用于确定事件上报信息，包括：根据所述业务描述信息和所述业务信息，向移动性管理实体或者能力开放实体发送事件关联信息，所述事件关联信息用于确定事件上报信息。
相应地，第十六方面，提供了一种通信装置，该通信装置具有实现上述第十三方面至 第十五方面的任一方面或实现的方法中通信装置行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
一种可能的实现方式中，所述通信装置包括：指示单元，用于指示用户面功能实体进行业务检测，所述业务为第一应用功能实体订阅的终端事件对应的业务；接收单元，用于接收所述用户面功能实体发送的业务检测通知，所述业务检测通知用于指示检测到所述业务的数据；监测单元，用于当终端不可达时，根据所述业务检测通知监测所述终端事件；以及发送单元，用于当监测到所述终端事件时，向网络开放功能实体或第一应用功能实体发送终端事件通知。
另一种可能的实现方式中，所述通信装置包括：处理器，所述处理器用于与存储器耦合，读取并执行所述存储器中的指令，以实现上述方法。
基于同一发明构思，由于该装置解决问题的原理以及有益效果可以参见上述各可能的通信装置的方法实施方式以及所带来的有益效果，因此该装置的实施可以参见方法的实施，重复之处不再赘述。
第十七方面，提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面或任意实现方式所述的方法。
第十八方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面或任意实现方式所述的方法。
附图说明
为了更清楚地说明本申请实施例或背景技术中的技术方案，下面将对本申请实施例或背景技术中所需要使用的附图进行说明。
图1为现有的EPS非漫游架构示意图；
图2为通过SCEF开放的3GPP EPS网络架构中接口的架构示意图；
图3a为5G的基于服务化接口的非漫游架构示意图；
图3b为5G的基于参考点的非漫游架构示意图；
图4为本申请实施例提供的一种应用功能实体向网络配置订阅终端事件的流程示意图；
图5a为示例的一种AF通过NEF向UDM/PCF配置订阅终端事件的流程示意图；
图5b为示例的一种AF通过PCF向UDR配置订阅终端事件的流程示意图；
图5c为示例的一种AF通过NEF向UDR配置订阅终端事件的流程示意图；
图6a为本申请实施例提供的一种通信方法的流程示意图；
图6b为本申请实施例提供的另一种通信方法的流程示意图；
图6c为一个具体示例的NEF进行终端事件通知的流程示意图；
图7a为一个示例的通信方法的流程示意图；
图7b为另一个示例的通信方法的流程示意图；
图7c为又一个示例的通信方法的流程示意图；
图7d为又一个示例的通信方法的流程示意图；
图7e为又一个示例的通信方法的流程示意图；
图8为本申请实施例提供的一种通信装置的模块示意图；
图9a为本申请实施例提供的另一种通信装置的模块示意图；
图9b为本申请实施例提供的又一种通信装置的模块示意图；
图10为本申请实施例提供的又一种通信装置的模块示意图；
图11为本申请实施例提供的又一种通信装置的模块示意图；
图12为本申请实施例提供的一种通信装置的硬件结构示意图；
图13本申请实施例提供的又一种通信方法的流程示意图；
图14a～图14f为又一个示例的通信方法的流程示意图；
图15为本申请实施例提供的又一种通信装置的模块示意图；
图16为本申请实施例提供的又一个通信方法的流程示意图；
图17为本申请实施例提供的又一个通信方法的流程示意图；
图18为本申请实施例提供的又一个通信方法的流程示意图；
图19为本申请实施例提供的又一个通信方法的流程示意图；
图20为本申请实施例提供的又一个通信方法的流程示意图。
具体实施方式
下面结合本申请实施例中的附图对本申请实施例进行描述。
本申请的技术方案可以应用于如图1所示的EPS网络的非漫游架构中，还可以应用于EPS网络的漫游架构中；还可以应用于下一代网络的非漫游架构和漫游架构中，例如，如图3a所示的第五代移动通信网络的基于服务化接口的非漫游架构中，以及如图3b所示的5G的基于参考点的非漫游架构中。
以图3a和图3b所示的5G的通信系统架构为例，该通信系统主要包括接入和移动性管理功能(access and mobility management function，AMF)实体、会话管理功能(Session Management Function，SMF)实体、用户面功能(user plane function，UPF)实体、网络开放功能(network exposure function，NEF)实体、以及应用功能(application function，AF)实体。还可以包括策略控制功能(policy control function，PCF)实体、统一数据库功能(unified data repository，UDR)实体和统一数据管理(unified data management，UDM)功能实体。需要说明的是，图3a和图3b中包括的功能实体及功能实体的功能可以是相同的，图3a中由于是基于服务化接口，一个功能实体发送给另一个功能实体的消息中需携带该另一个功能实体的标识；而图3b中由于是基于参考点，功能实体之间的消息是接口化消息，不需要携带功能实体的标识。
其中，图3a和图3b中的各功能实体的功能如下：
AMF实体：主要负责信令的处理，例如：接入控制、移动性管理、附着与去附着以及网关选择等功能。AMF实体为终端中的会话提供服务的情况下，会为该会话提供控制面的存储资源，以存储会话标识、与会话标识关联的SMF实体标识等。
SMF实体：主要负责会话管理，具体负责用户面功能实体的选择、用户面功能实体的重定向、因特网协议(internet protocol，IP)地址分配、承载的建立、修改和释放以及服务 质量(quality of service，QoS)的控制。
UPF实体：负责终端中用户数据的转发和接收。可以从数据网络接收用户数据，通过接入网设备传输给终端；还可以通过接入网设备从终端接收用户数据，转发到数据网络。UPF实体中为终端提供服务的传输资源和调度功能是由SMF实体进行管理控制的。
NEF实体：主要支持3GPP网络和第三方应用进行安全的交互。NEF能够安全的向第三方应用开放网络能力和事件，用于加强或者改善应用服务质量，3GPP网络同样可以安全的从第三方应用获取相关数据，用以增强网络的智能决策；同时该功能实体支持从UDR恢复结构化数据或者向UDR中存储结构化数据。
AF实体：主要支持与3GPP网络交互来提供服务，例如影响数据路由决策，策略控制功能，或者向网络侧提供一些业务服务(这些服务可以是第三方(3 rd party)的，也可以不是第三方的)。
PCF实体：主要支持提供统一的策略框架来控制网络行为，提供策略规则给控制层网络功能，同时负责获取与策略决策相关的用户签约信息。
UDR实体：主要负责存储结构化数据，存储的内容包括签约数据和策略数据、对外暴露的结构化数据和应用相关的数据。
UDM实体：主要用于管理用户签约信息。
需要说明的是，以上功能实体仅是一个名字，名字本身对实体不构成限定。例如，该会话管理功能实体也有可能被替换为“会话管理功能”或其它名字。而且，该会话管理功能实体也可以对应一个包括除了会话管理功能外还有其他功能的实体。用户面功能实体也有可能被替换为“用户面功能”或其它名字，而且，该用户面功能实体也可以对应一个包括除了用户面功能外还有其他功能的实体。在此进行统一说明，以下不再赘述。
终端通过无线接入网(radio access network，RAN)设备或接入网(access network，AN)设备接入网络。RAN设备主要是3GPP网络中的无线网络设备，AN可以是non-3GPP定义的接入网设备。
在本申请中，终端可以为用户设备(user equipment，UE)、手持终端、笔记本电脑、用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop，WLL)台、机器类型通信(machine type communication，MTC)终端或是其他可以接入网络的设备。
终端可以与无线接入网(radio access network，RAN)设备之间采用某种空口技术相互通信。RAN设备主要负责空口侧的无线资源管理、QoS管理、数据压缩和加密等功能。所述接入网设备可以包括各种形式的基站，例如：宏基站，微基站(也称为小站)，中继站，接入点等。在采用不同的无线接入技术的系统中，具备基站功能的设备的名称可能会有所不同，例如，在5G系统中，称为gNB；在长期演进(long term evolution，LTE)系统中，称为演进的节点B(evolved NodeB，eNB或者eNodeB)；在第三代(3rd generation，3G)系统中，称为节点B(Node B)等。
AN设备允许终端和3GPP核心网之间采用非3GPP技术互连互通，其中，非3GPP技 术例如：无线保真(wireless fidelity，Wi-Fi)、全球微波互联接入(worldwide interoperability for microwave Access，WiMAX)、码分多址(code division multiple access，CDMA)网络等。
在本申请中，终端处于不可用状态，是指网络为终端发起寻呼，但是没有收到响应，或者终端处于PSM模式，或者终端处于只允许MICO模式，等。其中，PSM模式是指允许终端减少能量损耗，不能立即可达来接收发送给终端的业务数据。MICO模式是指仅允许终端发起连接，当终端处于该模式，且终端处于空闲态时，网络认为终端不可达。
在本申请中，DDN失败可以是网络检测到终端处于不可用状态，或者触发DDN的数据的优先级(即分配和预留优先级(allocation and retention priority，ARP)，不高于之前触发DDN的数据的优先级。
在本申请中，终端事件可以是需要从网络获取各种类型的状态或信息的事件。例如，本申请的技术方案可以应用于高延迟通信的场景，终端事件可以是DDN失败后终端可用事件。提供该高延迟通信业务的应用功能实体能够通过订阅DDN失败后终端可用事件来支持对时延要求不高的业务通信。终端事件也可以是终端可达事件等。应用功能实体安装相关应用以提供对应的业务或服务。终端事件的订阅是指通过服务操作订阅事件通知或修改已经订阅的事件。
需要说明的是，本申请实施例中的术语“系统”和“网络”可被互换使用。“多个”是指两个或两个以上，鉴于此，本申请实施例中也可以将“多个”理解为“至少两个”。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，字符“/”，如无特殊说明，一般表示前后关联对象是一种“或”的关系。
本申请实施例提供一种通信方法及装置，对于管理特定业务的会话管理功能实体，向其订阅终端事件，会话管理功能实体在接收到用户面功能实体的业务检测通知时，通知接入和移动性管理功能实体监测终端事件，从而在5G架构中，可以针对特定的业务进行终端事件的订阅和监测。
本申请的向网络订阅终端事件以及激活终端事件、进行终端事件通知主要包括两个流程：
1)安装有应用的应用功能实体首先向网络配置终端事件。配置的途径又可以有以下几种：AF通过NEF向UDM/PCF配置事件；AF通过PCF向UDR配置事件；以及AF通过NEF向UDR配置事件等。下面将详细描述。
2)网络激活终端事件、通知终端事件。后面将通过详细的通信方法流程进行描述。
具体地，如图4所示，为本申请实施例提供的一种应用功能实体向网络配置订阅终端事件的流程示意图，该方法可包括以下步骤：
S101、应用功能实体发送第一消息给控制功能实体。该控制功能实体接收来自应用功能实体的第一消息。该第一消息用于订阅终端事件，该第一消息包括业务描述信息。
该第一消息还包括以下至少一个信息：终端事件对应的终端的标识、终端事件的事件类型信息、数据网络名称、切片信息和应用功能服务标识。
S102、控制功能实体分配该终端事件的事件关联标识。
S103、发送该业务描述信息、事件关联标识、终端的标识、终端事件的事件类型、数 据网络名称、切片信息和应用功能服务标识中的至少一个至统一数据库功能实体以便存储。
S104、该统一数据库功能实体存储以上至少一个信息。
本实施例以5G为例。对于某个业务，当需要对终端处理该业务过程中的状态进行监测时，提供该业务服务的应用功能实体可以向控制功能实体发送第一消息，该第一消息用于向网络订阅终端事件。该控制功能实体可以是UDM，PCF或NEF等。控制功能实体接收该第一消息。
在本实施例中，向网络订阅终端事件的可以是一个或多个应用功能实体。这多个应用功能实体订阅的终端事件对应的业务可以是相同的，也可以是不同的。例如，多个应用功能实体可以向多个终端订阅同一终端事件，也可以是多个应用功能实体向同一个终端订阅不同的终端事件。
在该第一消息中携带业务描述信息。该业务描述信息用于指示终端事件对应的业务。
该业务描述信息可以是业务数据的描述信息。例如，该业务描述信息可以是IP三元组(目的IP地址/IPv6前缀(IPv6 prefix)，端口号，IP上层协议号(如传输协议))，或应用标识(application ID)，或者非IP(non-IP)的描述符，或者以太网的业务描述信息，等任何能够识别特定应用功能实体的业务的描述信息。其中，目的IP地址可以是目的IPv4地址，或目的IPv6前缀，或目的IPv6地址。
相关功能实体可以根据业务描述信息区分该多个应用功能实体。另外，该第一消息还包括以下至少一个信息：终端事件对应的终端的标识、终端事件的事件类型信息、数据网络名称(data network name，DNN)、切片信息和应用功能服务标识(application function service identifier，AF-service-ID)。
其中，终端的标识可以是单个终端的标识(UE ID)，也可以是多个终端(即群组)的标识(group ID)。其中，终端标识可以是通用公共用户标识(generic public subscription identifier，GPSI)等用于识别用户的标识。群组标识可以是外部的群组标识。
其中，终端事件可以是需要从网络获取各种类型的状态或信息的事件，终端事件的事件类型也可以是定义的各种类型的终端事件。事件类型信息用于标识该终端事件。例如，本申请的技术方案可以应用于高延迟通信的场景，终端事件的事件类型可以是下行数据通知失败后终端可用事件。下行数据通知失败后终端可用事件是指应用功能实体通过网络向终端发送下行数据包时，若终端处于不可用状态，网络将激活该事件，监测终端的状态。当终端进入可用状态时，网络通过控制功能实体向应用功能实体上报终端可用状态。第三方应用能够通过订阅DDN失败后终端可用事件来支持对时延要求不高的业务通信。终端事件的事件类型也可以是终端可达事件等。终端事件的事件类型也可以是业务检测事件，用于向网络订阅当业务发生时，通知订阅者。事件类型信息可以用协议规定的事件类型的索引号表示，该事件类型信息预先存储在网络设备和终端设备。
其中，DNN用于标识用户访问的数据网络。切片信息可以是切片实例和/或单网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)。S-NSSAI或切片实例用于选择具体的切片网络，即核心网的网络，如SMF和UPF。AF-Service-id是一个应用功能服务的标识，网络侧可以根据该标识推导出DNN和切片信息。
此外，该第一消息还可以包括通知目标地址(notification target address)。通知目标地 址可以是NEF ID、AF ID或者AF地址。
控制功能实体接收该第一消息，对第一消息进行处理，包括根据本地策略检查该应用功能实体是否被授权执行该服务请求，该第一消息是否有问题，该应用功能实体的请求是否超过限额或者超过请求频率等。若检查通过，则控制功能实体存储以上信息，并分配一个该终端事件的事件关联标识。该事件关联标识用于标识终端事件和订阅该终端事件的功能实体之间的关联关系。该事件关联标识也可以称为通知关联标识(notification correlation ID)。或者该事件关联标识也可以是订阅关联标识(subscription correlation ID)，该订阅关联标识可以由AMF分配或者SMF分配。
另外，通知目标地址可以和通知关联ID联合使用：通知目标地址与通知关联ID用于将从事件提供者收到的通知和订阅关联起来。一个订阅和一个独立的通知目标地址与通知关联ID相关。
另外，若该控制功能实体为NEF，而向网络配置该终端事件的是UDM/PCF，则控制功能实体还可以向UDM/PCF发送订阅终端事件的消息。该消息包括业务描述信息，还包括以下至少一个信息：终端事件对应的终端的标识、终端事件的事件类型信息、DNN、切片信息和应用功能服务标识。
进一步地，控制功能实体检查消息是否有效，包括检查网络是否支持事件监测，请求是否在接收的范围等。检查通过时，该控制功能实体存储以上信息。
进一步地，控制功能实体还可以向UDR发送以上信息，由UDR进行统一存储。
具体地，控制功能实体发送业务描述信息、或者事件关联标识、或者终端的标识、或者终端事件的事件类型信息、或者数据网络名称、或者切片信息、或者应用功能服务标识、或者上述任意两者的组合、或者上述任意三者的组合、或者上述任意四者的组合、或者上述任意五者的组合、或者上述任意六者的组合、或者上述七者至统一数据库功能实体以便存储。
下面为示例的配置的途径：
示例一：AF通过NEF向UDM/PCF配置事件
如图5a所示，为示例的一种AF通过NEF向UDM/PCF配置订阅终端事件的流程示意图，该方法可包括以下步骤：
S201、AF确定向网络侧订阅“DDN失败后终端可用”事件。AF向NEF发送第一消息，该第一消息用于订阅终端事件。例如，在图3a所示的系统中，该消息可以是Nnef_EventExposure_subscribe。该订阅消息中包括以下信息：业务描述信息、终端标识(或者群组标识)、AF标识、事件类型信息、以及DNN/S-NSSAI/AF-Service-Id。
S202、NEF对消息进行处理，包括根据本地策略检查AF是否被授权执行该服务请求、该消息是否有问题、AF的请求是否超过限额或者超过请求频率等。若检查通过，则NEF存储以下信息：业务描述信息、终端标识(或者群组标识)、事件类型信息以及DNN/S-NSSAI/AF-Service-Id。并且NEF分配一个终端事件的事件关联标识(例如，NEF reference ID)。其中，事件关联标识用于标识终端事件和订阅终端事件的功能实体之间的关联关系。事件类型信息用于标识终端事件。可选地，NEF还可存储以下信息：AF标识或AF地址。可以通过AF标识或者AF地址找到AF、向AF发送消息。
S203、NEF向UDM/PCF发送第二消息，第二消息用于订阅终端事件。例如，在图3a所示的系统中，该消息可以是Nudm_EventExposure_subscribe/Npcf_EventExposure_subscribe。该订阅消息中包含以下信息：业务描述信息、终端标识(或者，可为群组标识)、事件类型信息、事件关联标识以及DNN/S-NSSAI/AF-Service-Id。可选地，该订阅消息还可包括AF标识或AF地址。所述事件类型信息为根据AF提供的事件类型信息确定，可以是相同的事件类型，或者用于支持AF订阅的事件产生的新的事件类型。
在另外的实施例中，接收到AF的事件信息后，NEF可以分别向UDM和PCF发送消息。其中向UDM发送的消息可以包含终端标识(或者，可为群组标识)、事件类型信息、事件关联标识。向PCF发送的消息包含终端标识(或者，可为群组标识)、事件类型信息、事件关联标识，业务描述信息和DNN/S-NSSAI/AF-Service-Id。其中所述事件类型信息为根据AF提供的事件类型信息确定，可以是相同的事件类型，或者用于支持AF订阅的事件产生的新的事件类型。可选的，NEF可以将AF-Service-Id映射为DNN/S-NSSAI，则存储的信息为DNN/S-NSSAI。
S204、UDM/PCF检查消息是否有效，包括检查网络是否支持事件监测，请求是否在接收的范围等。检查通过时，UDM/PCF存储业务描述信息、终端标识(或者群组标识)、AF标识、事件类型信息、事件关联标识以及DNN/S-NSSAI/AF-Service-Id。若NEF可以分别向UDM和PCF发送第二消息，所述UDM存储的信息为终端标识(或者群组标识)、AF标识、事件类型信息、事件关联标识；PCF存储业务描述信息、终端标识(或者群组标识)、AF标识、事件类型信息、事件关联标识以及DNN/S-NSSAI。可选的，UDM可以将AF-Service-Id映射为DNN/S-NSSAI，则存储的信息为DNN/S-NSSAI。
S205、进一步可选的，UDM/PCF可以向UDR发送第三消息，该第三消息用于订阅终端事件。例如，在图3a所示的系统中，该消息可以是Nudr_EventExposure_subscribe。UDR存储订阅该终端事件的上述信息。
示例二：AF通过PCF向UDR配置事件
如图5b所示，为示例的一种AF通过PCF向UDR配置订阅终端事件的流程示意图，该方法可包括以下步骤：
S301、AF确定向网络侧订阅“DDN失败后终端可用”事件。AF向PCF发送第一消息，该第一消息用于订阅终端事件。例如，在图3a所示的系统中，该消息可以是Npcf_EventExposure_subscribe。该订阅消息中包括以下信息：业务描述信息、终端标识(或者群组标识)、AF标识、事件类型信息以及DNN/S-NSSAI/AF-Service-Id。
S302、PCF对消息进行处理，包括根据本地策略检查AF是否授权执行该服务请求、该消息是否有问题、AF的请求是否超过限额或者超过请求频率等。若检查通过，则PCF存储以下信息：业务描述信息、终端标识(或者群组标识)、事件类型信息以及DNN/S-NSSAI/AF-Service-Id。并分配终端事件对应的事件关联标识(例如，PCF reference ID)。其中，事件关联标识用于标识终端事件和订阅终端事件的功能实体之间的关联关系。事件类型信息用于标识终端事件。可选地，该订阅消息还可包括AF标识或AF地址。
S303、进一步可选的，PCF向UDR发送第二消息，该第二消息用于订阅终端事件。例 如，在图3a所示的系统中，该消息可以是Nudr_EventExposure_subscribe)。该消息包括以下信息：业务描述信息、终端标识或者群组标识、事件类型信息、PCF reference ID以及DNN/S-NSSAI/AF-Service-Id。该订阅消息还可以包括AF标识或AF地址。
S304、可选的，UDR检查消息是否有效，包括检查网络是否支持事件监测，请求是否在接收的范围等。检查通过时，UDR存储以下信息：业务描述信息、终端标识或者群组标识、事件类型信息、PCF reference ID以及DNN/S-NSSAI/AF-Service-Id。UDR还可以存储AF标识或AF地址。
示例三：AF通过NEF向UDR配置事件
如图5c所示，为示例的一种AF通过NEF向UDR配置订阅终端事件的流程示意图，该方法可包括以下步骤：
S401、AF确定向网络侧订阅“DDN失败后终端可用”事件。AF向NEF发送第一消息，该第一消息用于订阅终端事件。例如，在图3a所示的系统中，该消息可以是Nnef_EventExposure_subscribe。该消息包括以下信息：业务描述信息、终端标识或者群组标识、AF标识、事件类型信息以及DNN/S-NSSAI/AF-Service-Id。
S402、NEF对消息进行处理，包括根据本地策略检查AF是否被授权执行该服务请求、该消息是否有问题、AF的请求是否超过限额或者超过请求频率等。若检查通过，则NEF存储以下信息：业务描述信息、终端标识或者群组标识、事件类型信息以及DNN/S-NSSAI/AF-Service-Id。并分配一个终端事件的事件关联标识(例如，NEF reference ID)。其中，事件关联标识用于标识终端事件和订阅终端事件的功能实体之间的关联关系。事件类型信息用于标识终端事件。NEF还可以存储AF标识或AF地址。
S403、NEF向UDR发送第二消息，该第二消息用于订阅终端事件。例如，在图3a所示的系统中，该消息可以是Nudr_EventExposure_subscribe。该消息中包括以下信息：业务描述信息、终端标识或者群组标识、事件类型信息、NEF reference ID以及DNN/S-NSSAI/AF-Service-Id。该消息还可以包括AF标识或AF地址。所述事件类型信息为根据AF提供的事件类型信息确定，可以是相同的事件类型，或者用于支持AF订阅的事件产生的新的事件类型。进一步可选的，NEF可以根据AF发送的事件信息生成多个事件，分别存储在UDR。
可选的，UDR检查消息是否有效，包括检查网络是否支持事件监测，请求是否在接收的范围等。检查通过时，UDR存储以下信息：业务描述信息、终端标识(或者群组标识)、事件类型信息、NEF reference ID以及DNN/S-NSSAI/AF-Service-Id。UDR还可以存储AF标识或AF地址。
根据本申请实施例提供的一种应用功能实体向网络配置订阅终端事件的方法，对于某个业务需要订阅终端事件，则应用功能实体向5G网络中的控制功能实体订阅该终端事件，具体在该业务执行时，控制功能实体再向具体的会话管理功能实体订阅该终端事件，从而实现5G架构下终端事件的订阅和监测。
下面对网络激活终端事件、通知终端事件的流程进行详细的描述：
图6a为本申请实施例提供的一种通信方法的流程示意图，该方法可包括以下步骤：
S501、控制功能实体根据数据网络名称、切片信息和应用功能服务标识中的至少一个 确定会话管理功能实体。
具体地，控制功能实体根据数据网络名称、切片信息和应用功能服务标识中的至少一个确定会话管理功能实体，可以是控制功能实体根据数据网络名称、或者根据切片信息、或者根据应用功能服务标识、或者根据数据网络名称和切片信息、或者根据数据网络名称和应用功能服务标识、或者根据切换信息和应用功能服务标识、或者根据数据网络名称、切片信息和应用功能服务标识，确定会话管理功能实体。
S502、该控制功能实体向该会话管理功能实体发送第一消息。该第一消息用于订阅终端事件，该第一消息包括业务描述信息，其中，该业务描述信息用于指示终端事件对应的业务。
S503、该会话管理功能实体向用户面功能实体发送第二消息。该第二消息用于指示用户面功能实体进行业务检测。该业务为被订阅的终端事件对应的业务。此外，另一种实施方式中，第二消息可以是业务信息请求，指示用户面功能实体上报业务信息，在该种情况下，则不需要进行S504。该业务信息可以是下行数据包的源IP地址(source IP address),源端口号(source port number)的至少一种，也可以一个索引信息，索引信息用于索引到特定的事件。该下行数据包可以为被丢弃的下行数据包。可选的，若下行数据通知失败，会话管理功能实体向用户功能实体发送业务信息请求。
S504、可选的，当收到的第二消息为用于指示用户面功能实体进行业务检测时，该用户面功能实体检测该业务。
S505、该用户面功能实体发送业务检测通知至会话管理功能实体。该业务检测通知用于指示业务数据的发生。会话管理功能实体接收该业务检测通知。在另一种实施方式中，该业务检测通知可以为业务信息，即在S503中的业务信息，该业务信息为根据下行数据包所确定。具体的，为根据接收到的下行数据包的包头所确定。例如，当下行数据包为IP数据包，其包头包含IP五元组信息；当下行数据包为以太数据包，其包头包含MAC地址。
S506、该会话管理功能实体响应于该业务检测通知，向接入与移动性管理功能实体发送监测终端事件的通知。可选的，该监测终端事件的通知可以包含事件关联信息，如事件关联标识(NEF Reference ID)。该事件关联信息用于确定事件上报信息。可选的，会话管理功能实体根据业务描述信息和业务信息，向移动性管理实体发送事件关联信息，即通过比较业务信息和业务描述信息，当业务信息和业务描述信息相匹配，则向移动性管理实体发送事件关联信息。
S507、接入与移动性管理功能实体监测被订阅的终端事件。
S508、当接入与移动性管理功能实体监测到该终端事件时，向订阅该终端事件的功能实体发送终端事件通知。其中，该终端事件通知包括以下至少一个信息：终端事件对应的终端的标识和终端事件的事件关联标识，该事件关联标识用于标识终端事件和订阅该终端事件的功能实体之间的关联关系。订阅该终端事件的功能实体接收该终端事件通知。
本实施例仍以5G为例。根据前面的描述，若AF欲向网络订阅终端事件，则向控制功能实体配置该终端事件的订阅。控制功能实体或者UDR保存终端事件对应的终端的标识、终端事件的事件类型信息、DNN、切片信息和应用功能服务标识、业务描述信息和事件关联标识。
在会话建立过程中，控制功能实体(例如UDM/PCF)接收到SMF发送的关联请求，该关联请求用于请求对该会话对应的业务进行事件订阅。该请求中可以包含DNN、切片信息、或者AF-service-ID。控制功能实体从本地或UDR中获取前述配置流程中配置的终端事件的DNN。控制功能实体确定该会话服务包括的DNN与前述配置流程中配置的终端事件的DNN一致，或控制功能实体从本地或UDR中获取前述配置流程中配置的终端事件的切片信息，确定该会话服务使用的切片信息与前述配置流程中配置的切片信息一致(若请求中包括AF-service-ID，也可以使用AF-service-ID推导出DNN和切片信息)，控制功能实体确定发送该关联请求的SMF，然后向SMF发送第一消息，该第一消息用于订阅终端事件。
或者在会话建立之后，控制功能实体接收到AF订阅的终端事件，确定有对应的DNN、切片信息的会话。控制功能实体确定关联与DNN、切片信息对应的会话的SMF，也可主动向SMF发送第一消息，用于订阅终端事件。
该第一消息包括业务描述信息，其中，该业务描述信息用于指示终端事件对应的业务，还可以用于确定为该终端提供服务的应用功能实体。
此外，该第一消息还可以包括终端事件的事件关联标识和事件类型信息。其中，事件关联标识用于标识终端事件和订阅终端事件的功能实体之间的关联关系，事件类型信息用于标识终端事件。事件关联标识可以是前述配置过程中控制功能实体生成的reference ID。该reference ID与AF ID关联。终端事件可以是需要从网络获取各种类型的状态或信息的事件，终端事件的事件类型也可以是定义的各种类型的终端事件。例如，终端事件的事件类型包括DDN失败后终端可用通知事件、终端可达事件等。事件类型，也可以用event ID来表示。event ID表示正在被订阅的事件类型，例如availability after DDN failure。
SMF接收该第一消息。并向UPF发送第二消息。该第二消息用于指示UPF进行业务检测。该业务为被订阅的终端事件对应的业务，即业务描述信息对应的业务。该第二消息可以是SMF向UPF下发相应的规则，根据该规则检测业务数据。
UPF接收数据网络发送的下行数据，根据包检测规则(packet detection rule，PDR)，例如包过滤器(packet filter)，或指示(indicator)等检测到被订阅的终端事件对应的业务。该包检测规则包括业务描述信息，例如IP三元组。
例如，该规则可以是当在UPF中未存储该会话的接入网隧道信息时，需要建立用户面隧道向终端发送该下行数据，则UPF向SMF发送业务检测通知。该业务检测通知用于指示业务数据的发生。该业务数据为业务描述信息对应的业务数据。
另外，在本实施例中，业务描述信息可以通过事件过滤器信息来表示。事件过滤器信息(event filter information)，用于确定匹配通知事件的条件。其中事件过滤器信息包括事件参数类型(event parameter types)和事件参数值(event parameter value(s))。其中事件参数类型可以是业务描述信息。事件参数值可以是具体的业务描述信息，如IP三元组，Application ID。
SMF接收该业务检测通知。并响应于该业务检测通知。向AMF发送监测终端事件的通知。
AMF检测终端的状态。
以终端事件为DDN失败后终端可用通知事件为例，若AMF或者SMF检测到终端处 于不可用状态，则激活终端事件，监测被订阅的终端事件。其中，终端处于不可用状态，是指网络为终端发起寻呼，但是没有收到响应，或者终端处于PSM模式，或者终端处于MICO模式。
当AMF检测到终端连接至网络时，例如终端发起跟踪区更新(tracking area update，TAU)请求或者服务请求(service request)，则AMF向订阅该终端事件的功能实体发送终端事件通知。其中，该终端事件通知包括以下至少一个信息：终端事件对应的终端的标识和终端事件的事件关联标识，该事件关联标识用于标识终端事件和订阅该终端事件的功能实体之间的关联关系。订阅该终端事件的功能实体接收该终端事件通知。
其中，若一个AF向多个终端订阅同一个终端事件，则根据终端事件通知中的终端的标识，可以区分订阅该终端事件的AF；若多个AF向同一个终端订阅多个终端事件，则根据终端事件通知中的事件关联标识，可以区分订阅该终端事件的AF；若多个AF向多个终端订阅多个终端事件，则根据终端事件通知中的终端的标识和事件关联标识，可以区分订阅该终端事件的AF。从而可以由一个或多个应用功能实体为终端提供业务服务，在订阅终端事件时，通过业务描述信息指示终端事件对应的业务，从而可以区分订阅终端事件的应用功能实体。
其中，订阅该终端事件的功能实体可以是SMF、AF或NEF。
若该终端事件的事件类型为DDN失败后终端可用事件，则AF在接收到该终端事件通知(通知终端可用)后，可以重新向该终端发送下行数据。
其中，可以采用事件上报信息(event reporting information)用于标识上报的事件信息。在本实施例中，可以用于描述AMF或者SMF上报的availability after DDN failure事件上报信息。
图6b为本申请实施例提供的一种通信方法的流程示意图，该方法可包括以下步骤：
S501’、控制功能实体根据数据网络名称、切片信息和应用功能服务标识中的至少一个确定会话管理功能实体。
具体地，控制功能实体根据数据网络名称、切片信息和应用功能服务标识中的至少一个确定会话管理功能实体，可以是控制功能实体根据数据网络名称、或者根据切片信息、或者根据应用功能服务标识、或者根据数据网络名称和切片信息、或者根据数据网络名称和应用功能服务标识、或者根据切换信息和应用功能服务标识、或者根据数据网络名称、切片信息和应用功能服务标识，确定会话管理功能实体。
S502’、该控制功能实体向该会话管理功能实体发送第一消息。该第一消息用于订阅终端事件，该第一消息包括业务描述信息，其中，该业务描述信息用于指示终端事件对应的业务。
S503’、该会话管理功能实体向用户面功能实体发送第二消息。该第二消息用于指示用户面功能实体进行业务检测。该业务为被订阅的终端事件对应的业务。此外，另一种实施方式中，第二消息可以是业务信息请求，指示用户面功能实体上报业务信息，在该种情况下，则不需要进行S504’。该业务信息可以是下行数据包的源IP地址，源端口号的至少一种，也可以一个索引信息，索引信息用于索引到特定的事件。该下行数据包可以为被丢弃的下行数据包。可选的，若下行数据通知失败，会话管理功能实体向用户功能实体发送业 务信息请求。
S504’、可选的，当收到的第二消息为用于指示用户面功能实体进行业务检测时，该用户面功能实体检测该业务。
S505’、该用户面功能实体发送业务检测通知至会话管理功能实体。该业务检测通知用于指示业务数据的发生。会话管理功能实体接收该业务检测通知。在另一种实施方式中，该业务检测通知可以为业务信息，即在S503’中的业务信息，该业务信息为根据下行数据包所确定。具体的，为根据接收到的下行数据包的包头所确定。例如，当下行数据包为IP数据包，其包头包含IP五元组信息；当下行数据包为以太数据包，其包头包含MAC地址。
上述步骤的实现可分别参考图6a所示实施例的步骤S501～S505，在此不再赘述。
S506’、该会话管理功能实体响应于该业务检测通知，向网络开放功能实体发送终端业务发生通知。
在前述步骤中，会话管理实体接收到控制功能实体的终端事件的订阅。则会话管理功能实体在接收到用户面功能实体发送的业务检测通知后，并且确定终端不可达时，向NEF发送终端业务发生通知。
S507’、当网络开放功能实体接收到终端可达通知时，向订阅该终端事件的功能实体发送终端事件通知。其中，该终端事件通知包括以下至少一个信息：终端事件对应的终端的标识和终端事件的事件关联标识，该事件关联标识用于标识终端事件和订阅该终端事件的功能实体之间的关联关系。订阅该终端事件的功能实体接收该终端事件通知。
由于之前NEF接收到了SMF的终端业务发生通知，则当NEF接收到AMF发送的终端可达通知时，NEF向AF发送终端事件通知。根据本申请实施例提供的一种通信方法，SMF接收终端事件的订阅，并且在终端不可达时，通知NEF，且在NEF接收到AMF发送的终端可达通知时，向AF发送终端事件通知，从而实现了在5G架构下，针对特定的业务进行终端事件的订阅和通知。
图6c为一种具体示例的NEF进行终端事件通知的流程示意图。其中：
S501”、UDM/PCF根据DNN/S-NSSAI/AF-service-ID确定目标SMF，向SMF和AMF订阅终端事件。
该DNN/S-NSSAI/AF-service-ID可以是从UDR获取的或者本地存储的。
UDM或者PCF向AMF和SMF订阅终端事件，可以有下面两种方式：
方法一：UDM或PCF向AMF发送事件1(如DDN失败UE可用事件)事件关联标识和SMF发送事件2(如业务检测事件)，事件关联标识，业务描述信息。
方法二：UDM向AMF发送事件1(如DDN失败UE可用事件)事件关联标识，PCF向SMF发送事件2(如业务检测事件)，事件关联标识，业务描述信息。
S502a”、UDM/PCF向AMF发送第一消息。
S502b”、UDM/PCF向目标SMF发送第二消息(例如，Nsmf_EventExposure)。
该第二消息中包含业务描述信息、事件类型信息和事件关联标识(例如，NEF reference ID)，还可以包括NEF ID等信息。在本示例中，事件类型为业务检测事件。
SMF/AMF接收该第一消息。
具体地，SMF在收到了业务检测事件和业务描述信息后，SMF把这两者关联到一起。 这两者在一起发送(在同一个消息中发送)就代表它们是关联在一起，或者业务描述信息在业务检测事件订阅消息中发送，代表它们关联在一起。
S503”、SMF通过N4会话建立或者修改流程向UPF发送业务检测消息。该业务检测消息包括业务描述信息。
具体地，SMF在收到UPF的检测到业务描述信息对应的数据的通知时，可以确定是哪个事件对应的数据触发的事件，因此就向相应的NEF发送事件关联标识。
UPF根据该业务检测消息，检测对应的业务。即检测业务描述信息对应的业务。
此外，另一种实施方式中，业务检测消息可以是业务信息请求，指示用户面功能实体上报业务信息。该业务信息可以是下行数据包的源IP地址，源端口号的至少一种，也可以一个索引信息，索引信息用于索引到特定的事件。该下行数据包可以为被丢弃的下行数据包。可选的，若下行数据通知失败，会话管理功能实体向用户功能实体发送业务信息请求。
S504”、AMF向SMF发送UE不可达信息。
AMF可以在接收到其它AF发送的业务数据，并且检测到UE不可达时，向SMF发送UE不可达信息；或者AMF在接收到AF发送的业务数据，且检测到DDN数据失败时，向SMF发送UE不可达信息。
可选地，S504”可以是在S506”之前的任一个步骤。
S505”、AF向终端发送下行数据包。
S506”、UPF向SMF发送业务检测通知。
UPF根据包检测规则，检测到该下行数据包为被订阅的终端事件对应的业务。
当UPF中未存储该会话的接入隧道信息时，需要建立用户面隧道，UPF向SMF发送业务检测通知。该业务检测通知用于指示检测到业务数据的发生。
具体地，被订阅的终端事件对应的业务，即业务描述信息对应的业务。该包检测规则包括业务描述信息。例如，该业务描述信息为IP五元组，UPF根据该IP五元组检测接收到的下行数据包。当检测到与该IP五元组对应的下行数据包时，确认检测到业务数据的发生。
在另一种实施方式中，该业务检测通知可以为业务信息，即在S503”中的业务信息，该业务信息为根据下行数据包所确定。具体的，为根据接收到的下行数据包的包头所确定。例如，当下行数据包为IP数据包，其包头包含IP五元组信息；当下行数据包为以太数据包，其包头包含MAC地址。
S507”、SMF向NEF发送事件通知。
具体地，SMF通知NEF终端业务发生。
S508a”、若SMF在UE不可达时向NEF上报事件时，则执行本步骤，NEF记录事件。
S508b”、若SMF在任何时候检测到业务都向NEF上报事件时，NEF记录事件，NEF判断UE不可达状态。
S509”、终端向网络发起连接。
例如，终端向网络发起TAU请求或服务请求。
S510”、AMF向NEF发送UE可达事件通知。
S511”、NEF向AF发送UE终端事件通知。
具体地，对应于S508a”、当接收到UE可达事件时，根据记录，向AF发送事件。例如，向记录的业务对应事件的AF发送UE可达事件。
对应于S508b”、若UE可达，删除记录。若不可达，保存记录，当接收到UE可达事件时，根据记录，向AF发送事件。如向记录的业务对应事件的AF发送UE可达事件。
下面结合具体的通信场景，对上述通信方法进行进一步详细的示例描述：
示例一：AMF从SMF接收终端事件的订阅，执行事件监测和通知
如图7a所示，为一个示例的通信方法的流程示意图。在该示例中，由SMF通知AMF进行终端事件的监测。具体地，在会话建立过程中或者会话建立之后UDM/PCF执行下面流程：
S601、UDM/PCF根据DNN/S-NSSAI/AF-service-ID确定目标SMF。该DNN/S-NSSAI/AF-service-ID可以从UDR获取的或者本地存储的。
S602、UDM/PCF向目标SMF发送第一消息(例如，Nsmf_EventExposure)。该第一消息中包含业务描述信息、事件类型信息和事件关联标识(例如，NEF reference ID)，还可以包括NEF ID等信息。在本示例中，事件类型为DDN失败后终端可用事件。
SMF接收该第一消息。
具体地，SMF在收到了availability after DDN failure事件和业务描述信息后，SMF把这两者关联到一起。这两者在一起发送(在同一个消息中发送)就代表它们是关联在一起，或者业务描述信息在availability after DDN failure事件订阅消息中发送，代表它们关联在一起。
S603、SMF通过N4会话建立或者修改流程向UPF发送业务检测消息。该业务检测消息包括业务描述信息。
具体地，SMF在收到UPF的检测到业务描述信息对应的数据的通知时，可以确定是哪个事件对应的数据触发的事件，因此就向相应的AMF发送事件关联标识。此外，另一种实施方式中，该业务检测消息可以是业务信息请求，指示用户面功能实体上报业务信息，在该种情况下，则不需要进行S605。该业务信息可以是下行数据包的源IP地址，源端口号的至少一种，也可以一个索引信息，索引信息用于索引到特定的事件。该下行数据包可以为被丢弃的下行数据包。可选的，若下行数据通知失败，会话管理功能实体向用户功能实体发送业务信息请求。
UPF根据该业务检测消息，检测对应的业务。即检测业务描述信息对应的业务。
S604、AF向终端发送下行数据包。
S605、可选的，当收到的业务检测消息为用于指示用户面功能实体进行业务检测时，UPF根据包检测规则，检测到该下行数据包为被订阅的终端事件对应的业务。
当UPF中未存储该会话的接入隧道信息时，需要建立用户面隧道，UPF向SMF发送业务检测通知。该业务检测通知用于指示检测到业务数据的发生。
具体地，被订阅的终端事件对应的业务，即业务描述信息对应的业务。该包检测规则包括业务描述信息。例如，该业务描述信息为IP三元组，UPF根据该IP三元组检测接收到的下行数据包。当检测到与该IP三元组对应的下行数据包时，确认检测到业务数据的发生。
S606、SMF响应于UPF发送的业务检测通知，向AMF发送第二消息(例如，Namf_CommunicationN1N2MessageTransfer)。该第二消息中包括事件类型信息和事件关联标识(例如，NEF reference ID)，还可以包括NEF ID。NEF ID用于AMF可以向该NEF ID对应的NEF发送通知。
作为S606的一种替换方式，事件类型信息和事件关联标识可以在不同的消息中携带。例如，SMF可以在Namf_CommunicationN1N2MessageTransfer中携带NEF reference ID，在Namf_EventExposure_Subscribe中携带事件类型信息。另外，两个消息的顺序没有先后之分。在另一种实施方式中，该业务检测通知可以为业务信息，即在S603中的业务信息，该业务信息为根据下行数据包所确定。具体的，为根据接收到的下行数据包的包头所确定。例如，当下行数据包为IP数据包，其包头包含IP五元组信息；当下行数据包为以太数据包，其包头包含MAC地址。
S607、AMF检测到终端不可用，AMF向SMF发送响应消息(例如，Namf_CommunicationN1N2MessageTransfer)，通知DDN失败。
S608、SMF进一步向UPF发送DDN失败指示。
S609、当AMF确定终端不可用时，AMF设置或激活DDN失败后可用事件，AMF开始监测终端的可用性状态。
S610、终端向网络发起连接。例如，终端向网络发起TAU请求或服务请求。
S611、AMF确定本地设置DDN失败后可用事件，则向NEF发送终端事件通知(例如，Namf_EventExposure_Notify)。该终端事件通知中包括以下至少一个信息：终端标识和事件关联标识(例如，NEF reference ID)。
S612、NEF根据终端的标识和/或NEF reference ID向AF发送终端事件通知(例如，Namf_EventExposure_Notify)。
AF在接收到该终端事件通知后，确定终端可用，可以重新向终端发送下行数据。
示例二：SMF执行事件监测和通知
如图7b所示，为另一个示例的通信方法的流程示意图。与7a所示的示例不同的是，在该示例中，AMF进行终端可达事件的监测，在AMF监测到终端可达时，向会话管理功能实体发送终端可达通知，该通知用于指示SMF进行DDN失败后终端可用事件的监测。具体地，在会话建立过程中或者会话建立之后UDM/PCF执行下面的流程：
S701、UDM/PCF根据DNN/S-NSSAI/AF-service-ID确定目标SMF。该DNN/S-NSSAI/AF-service-ID为从UDR获取的或者本地存储的。
S702、UDM/PCF向目标SMF发送第一消息(例如，Nsmf_EventExposure)。该第一消息中包含业务描述信息、事件类型信息和事件关联标识(例如，NEF reference ID)，还可以包括NEF ID等信息。在本示例中，该事件类型为DDN失败后终端可用事件。
S703、SMF通过N4会话建立或者修改流程向UPF发送业务检测消息。该业务检测消息用于指示UPF检测被订阅的终端事件对应的业务，即业务描述信息对应的业务。此外，另一种实施方式中，该业务检测消息可以是业务信息请求，指示用户面功能实体上报业务信息，在该种情况下，则不需要进行S705。该业务信息可以是下行数据包的源IP地址，源端口号的至少一种，也可以一个索引信息，索引信息用于索引到特定的事件。该下行数据 包可以为被丢弃的下行数据包。可选的，若下行数据通知失败，会话管理功能实体向用户功能实体发送业务信息请求。
S704、AF向终端发送下行数据包。
S705、可选的，当收到的业务检测消息为用于指示用户面功能实体进行业务检测时，UPF根据包检测规则，确定该下行数据包为被订阅的终端事件对应的业务，且需要建立用户面隧道时，UPF向SMF发送业务检测通知。该业务检测通知用于指示检测到业务数据的发生。
S706、SMF响应于UPF发送的业务检测通知，向AMF发送第二消息(例如，Namf_CommunicationN1N2MessageTransfer)。该第二消息用于订阅终端事件，该第二消息包括事件类型信息。该事件类型为终端可达事件。
S707、AMF检测到终端不可达，则向SMF发送响应消息(例如，Namf_CommunicationN1N2MessageTransfer)。该响应消息用于指示终端不可达。
S708、SMF进一步向UPF发送DDN失败指示。
S709、AMF激活终端可达事件。
S710、当SMF确定终端不可用时(如终端处于PSM状态或者终端处于MICO状态等)，SMF设置DDN失败后可用事件。
终端向网络发起连接。例如，终端向网络发起TAU请求或服务请求。
S711、AMF确定SMF订阅了终端可达上报事件，则向SMF发送第一终端事件通知(例如，Namf_EventExposure_Notify)。该第一终端事件通知用于通知终端可达。
S712a、SMF确定设置DDN失败后可用事件，向NEF发送第二终端事件通知。该第二终端事件通知包括以下至少一个信息：终端的标识和终端事件的事件关联标识。
S713、NEF根据终端的标识和/或事件关联标识向AF发送该第二终端事件通知。
作为S712a和S713的替换方式，也可以执行S712b、SMF可以向AF发送第二终端事件通知。该第二终端事件通知包括以下至少一个信息：AF的标识、终端的标识和终端事件的事件关联标识。
AF在接收到该终端事件通知后，确定终端可用，可以重新向终端发送下行数据。
示例三：SMF执行业务检测，AMF从UDM/PCF接收终端事件的订阅并执行事件检测和通知
如图7c所示，为又一个示例的通信方法的流程示意图。具体的流程描述如下：
S801、UDM/PCF(SMF-PCF)根据DNN/S-NSSAI/AF-service-ID确定目标SMF。其中，DNN/S-NSSAI/AF-service-ID为从UDR获取的或者本地存储的。进一步的，UDM/PCF(AMF-PCF)根据UE标识确定AMF。
S802、在终端注册过程中或者注册状态的任何其他时间，UDM/PCF(AMF-PCF)向AMF发送第一消息(例如，Nsmf_EventExposure)。该第一消息包括事件类型信息和事件关联标识(例如，NEF reference ID)，还可以包括NEF ID。在本示例中，事件类型为DDN失败后终端可用事件。
在会话建立过程中或者会话建立之后，UDM/PCF(SMF-PCF)向目标SMF发送第二消息(例如，Nsmf_EventExposure服务消息)。该第二消息中包含业务描述信息和事件关联 标识(例如，NEF reference ID)。
其中，AMF-PCF指的是与AMF建立关联的PCF，用于向AMF提供接入和移动性相关的策略、终端策略。SMF-PCF指的是与SMF建立关联的PCF，用于向SMF提供会话相关的策略。AMF-PCF和SMF-PCF可以是同一个功能实体，也可以是独立的功能实体。
S803、SMF通过N4会话建立或者修改流程向UPF发送业务检测消息。该业务检测消息用于指示UPF检测被订阅的终端事件对应的业务，即业务描述信息对应的业务。此外，另一种实施方式中，该业务检测消息可以是业务信息请求，指示用户面功能实体上报业务信息，在该种情况下，则不需要进行S805。该业务信息可以是下行数据包的源IP地址，源端口号的至少一种，也可以一个索引信息，索引信息用于索引到特定的事件。该下行数据包可以为被丢弃的下行数据包。可选的，若下行数据通知失败，会话管理功能实体向用户功能实体发送业务信息请求。
S804、AF向终端发送下行数据包。
S805、可选的，当收到的第二消息为用于指示用户面功能实体进行业务检测时，UPF接收该下行数据包，根据包检测规则确定该下行数据包为被订阅的终端事件对应的业务，且需要建立用户面隧道时，UPF向SMF发送下行数据通知。该下行数据通知用于指示业务数据的发生。在另一种实施方式中，该下行数据通知可以为业务信息，即在S803中的业务信息，该业务信息为根据下行数据包所确定。具体的，为根据接收到的下行数据包的包头所确定。例如，当下行数据包为IP数据包，其包头包含IP五元组信息；当下行数据包为以太数据包，其包头包含MAC地址。
S806、SMF响应于UPF发送的业务检测通知，向AMF发送第三消息(例如，Namf_CommunicationN1N2MessageTransfer)。该第三消息中包括NEF reference ID，还可以包括NEF ID。需要说明的是，在本实施例中，SMF是在第三消息中激活AMF进行终端事件的监测，这时，SMF是通知AMF开始监测终端事件，而UDM/PCF已经在第一消息中配置AMF进行终端事件的监测。即配置监测终端事件与检测到业务描述信息对应的业务可以是独立的过程，两者可以是在不同的消息中指示的。可选的，该第三消息可以包含事件关联信息，如事件关联标识。该事件关联信息用于确定事件上报信息。可选的，会话管理功能实体根据业务描述信息和业务信息，向移动性管理实体发送事件关联信息，即通过比较业务信息和业务描述信息，当业务信息和业务描述信息相匹配，则向移动性管理实体发送事件关联信息。
在上述流程中，事件订阅消息和事件监测通知是由不同的功能实体或分别由SMF发送。AMF首先收到了availability after DDN failure的事件订阅信息，然后AMF收到了事件监测通知，其中包括NEF reference ID，那么AMF可以把这监测通知和这个事件关联到一起。S807、AMF检测到终端不可用，下行数据通知失败，AMF向SMF发送响应消息(例如，Namf_CommunicationN1N2MessageTransfer)，通知DDN失败。
S808、SMF进一步向UPF发送DDN失败指示。
S809、当AMF确定UE不可用时(如UE处于PSM状态或者UE处于MICO状态等)，根据NEF reference ID，AMF设置或激活对应的DDN失败后终端可用事件。S810、终端向网络发起连接。例如，终端向网络发起TAU请求或服务请求。
S811、AMF确定本地设置DDN失败后终端可用事件，则向NEF发送终端事件通知(例如，Namf_EventExposure_Notify)。该终端事件通知包括以下至少一个信息：终端的标识和NEF reference ID。
在本示例中，一个或多个AF订阅终端事件，AMF关联方式主要有两种：(1)AMF上是只为一个UE订阅一个availability after DDN failure的事件，然后这个事件可以有不同的NEF Reference ID，从而AMF可以通过NEF向不同的AF上报这个事件，这是一种方式。(2)另一种方式是为UE服务的每个AF可以为每个事件向AMF订阅这个availability after DDN failure事件，这样每个availability after DDN failure事件可能对应着不同的AF。
作为一种可选的方式，AMF也可以直接向AF上报这个事件。
S812、NEF根据终端的标识和/或事件关联标识向AF发送终端事件通知(例如，Namf_EventExposure_Notify)。
AF在接收到该终端事件通知后，确定终端可用，可以重新向终端发送下行数据。根据本申请实施例提供的一种通信方法，对于管理特定业务的会话管理功能实体，向其订阅终端事件，会话管理功能实体在接收到用户面功能实体的业务检测通知时，通知接入和移动性管理功能实体监测终端事件，从而在5G架构中，可以针对特定的业务进行终端事件的订阅和监测。
示例四：漫游场景下，V-SMF执行事件监测和通知
如图7d所示，为又一个示例的通信方法的流程示意图。与7b所示的示例不同的是，本地会话管理功能实体(H-SMF)向漫游地会话管理功能实体(V-SMF)转发DDN失败后终端可用事件订阅消息，由V-SMF执行事件监测和通知。具体地，在会话建立过程中或者会话建立之后UDM/PCF执行下面的流程：
S701’、UDM/PCF根据DNN/S-NSSAI/AF-service-ID确定目标H-SMF。该DNN/S-NSSAI/AF-service-ID为从UDR获取的或者本地存储的。
S702a’、UDM/PCF向目标H-SMF发送第一消息(例如，Nsmf_EventExposure)。该第一消息中包含业务描述信息、事件类型信息和事件关联标识(例如，NEF reference ID)，还可以包括NEF ID等信息。在本示例中，该事件类型为DDN失败后终端可用事件。
S702b’、H-SMF向V-SMF发送该第一消息。
S703’、V-SMF通过N4会话建立或者修改流程向漫游地用户面功能实体(V-UPF)发送业务检测消息。该业务检测消息用于指示V-UPF检测被订阅的终端事件对应的业务，即业务描述信息对应的业务。此外，另一种实施方式中，该业务检测消息可以是业务信息请求，指示用户面功能实体上报业务信息，在这种情况下，则不需要进行S705’。该业务信息可以是下行数据包的源IP地址，源端口号的至少一种，也可以一个索引信息，索引信息用于索引到特定的事件。该下行数据包可以为被丢弃的下行数据包。可选的，若下行数据通知失败，会话管理功能实体向用户功能实体发送业务信息请求。
S704’、AF向终端发送下行数据包。
S705’、可选的，当收到的业务检测消息为用于指示用户面功能实体进行业务检测时，V-UPF根据包检测规则，确定该下行数据包为被订阅的终端事件对应的业务，且需要建立用户面隧道时，V-UPF向V-SMF发送业务检测通知。该业务检测通知用于指示检测到业务 数据的发生。在另一种实施方式中，该业务检测通知可以为业务信息，即在S703’中的业务信息，该业务信息为根据下行数据包所确定。具体的，为根据接收到的下行数据包的包头所确定。例如，当下行数据包为IP数据包，其包头包含IP五元组信息；当下行数据包为以太数据包，其包头包含MAC地址。
S706’、V-SMF响应于V-UPF发送的业务检测通知，向AMF发送第二消息(例如，Namf_CommunicationN1N2MessageTransfer)。该第二消息用于订阅终端事件，该第二消息包括事件类型信息。该事件类型为终端可达事件。可选的，该第二消息可以包含事件关联信息，如事件关联标识。该事件关联信息用于确定事件上报信息。可选的，会话管理功能实体根据业务描述信息和业务信息，向移动性管理实体发送事件关联信息，即通过比较业务信息和业务描述信息，当业务信息和业务描述信息相匹配，则向移动性管理实体发送事件关联信息。
S707’、AMF检测到终端不可达，则向V-SMF发送响应消息(例如，Namf_CommunicationN1N2MessageTransfer)。该响应消息用于指示终端不可达。
S708’、V-SMF进一步向V-UPF发送DDN失败指示。
S709’、AMF激活终端可达事件。
S710’、当V-SMF确定终端不可用时(如终端处于PSM状态或者终端处于MICO状态等)，V-SMF设置DDN失败后可用事件。
终端向网络发起连接。例如，终端向网络发起TAU请求或服务请求。
S711’、AMF确定V-SMF订阅了终端可达上报事件，则向V-SMF发送第一终端事件通知(例如，Namf_EventExposure_Notify)。该第一终端事件通知用于通知终端可达。
S712a’、V-SMF确定设置DDN失败后可用事件，向NEF发送第二终端事件通知。该第二终端事件通知包括以下至少一个信息：终端的标识和终端事件的事件关联标识。
S713’、NEF根据终端的标识和/或事件关联标识向AF发送该第二终端事件通知。
作为S712a’和S713’的替换方式，也可以执行S712b’、V-SMF可以向AF发送第二终端事件通知。该第二终端事件通知包括以下至少一个信息：AF的标识、终端的标识和终端事件的事件关联标识。
AF在接收到该终端事件通知后，确定终端可用，可以重新向终端发送下行数据。
示例五：在漫游场景下，V-SMF执行业务检测，AMF从UDM/PCF接收终端事件的订阅并执行事件检测和通知
如图7e所示，为又一个示例的通信方法的流程示意图。具体的流程描述如下：
S801’、UDM/PCF(SMF-PCF)根据DNN/S-NSSAI/AF-service-ID确定目标H-SMF。其中，DNN/S-NSSAI/AF-service-ID为从UDR获取的或者本地存储的。进一步的，UDM/PCF(AMF-PCF)根据UE标识确定AMF。
S802a’、在终端注册过程中或者注册状态的任何其他时间，UDM/PCF(AMF-PCF)向AMF发送第一消息(例如，Nsmf_EventExposure)。该第一消息包括事件类型信息和事件关联标识(例如，NEF reference ID)，还可以包括NEF ID。在本示例中，事件类型为DDN失败后终端可用事件。
S802b’、在会话建立过程中或者会话建立之后，UDM/PCF(SMF-PCF)向目标H-SMF 发送第二消息(例如，Nsmf_EventExposure服务消息)。该第二消息中包含业务描述信息和事件关联标识(例如，NEF reference ID)。
其中，AMF-PCF指的是与AMF建立关联的PCF，用于向AMF提供接入和移动性相关的策略、终端策略。SMF-PCF指的是与H-SMF建立关联的PCF，用于向H-SMF提供会话相关的策略。AMF-PCF和SMF-PCF可以是同一个功能实体，也可以是独立的功能实体。
S802b”、H-SMF向V-SMF发送第三消息。该第三消息中包括业务描述信息和事件关联标识。
S803’、V-SMF通过N4会话建立或者修改流程向V-UPF发送业务检测消息。该业务检测消息用于指示V-UPF检测被订阅的终端事件对应的业务，即业务描述信息对应的业务。此外，另一种实施方式中，业务检测消息可以是业务信息请求，指示用户面功能实体上报业务信息，在该种情况下，则不需要进行S805’。该业务信息可以是下行数据包的源IP地址，源端口号的至少一种，也可以一个索引信息，索引信息用于索引到特定的事件。该下行数据包可以为被丢弃的下行数据包。可选的，若下行数据通知失败，会话管理功能实体向用户功能实体发送业务信息请求。
S804’、AF向终端发送下行数据包。
S805’、可选的，当收到的业务检测消息为用于指示用户面功能实体进行业务检测时，V-UPF接收该下行数据包，根据包检测规则确定该下行数据包为被订阅的终端事件对应的业务，且需要建立用户面隧道时，V-UPF向V-SMF发送下行数据通知。该下行数据通知用于指示业务数据的发生。
S806’、V-SMF响应于V-UPF发送的业务检测通知，向AMF发送第四消息(例如，Namf_CommunicationN1N2MessageTransfer)。该第四消息中包括NEF reference ID，还可以包括NEF ID。需要说明的是，在本实施例中，V-SMF是在第四消息中激活AMF进行终端事件的监测，这时，V-SMF是通知AMF开始监测终端事件，而UDM/PCF已经在第一消息中配置AMF进行终端事件的监测。即配置监测终端事件与检测到业务描述信息对应的业务可以是独立的过程，两者可以是在不同的消息中指示的。
在上述流程中，事件订阅消息和事件监测通知是由不同的功能实体或分别由V-SMF发送。AMF首先收到了availability after DDN failure的事件订阅信息，然后AMF收到了事件监测通知，其中包括NEF reference ID，那么AMF可以把这监测通知和这个事件关联到一起。在另一种实施方式中，该业务检测通知可以为业务信息，即在S803’中的业务信息，该业务信息为根据下行数据包所确定。具体的，为根据接收到的下行数据包的包头所确定。例如，当下行数据包为IP数据包，其包头包含IP五元组信息；当下行数据包为以太数据包，其包头包含MAC地址。
可选的，该第四消息可以包含事件关联信息，如事件关联标识(NEF Reference ID)。该事件关联信息用于确定事件上报信息。可选的，会话管理功能实体根据业务描述信息和业务信息，向移动性管理实体发送事件关联信息，即通过比较业务信息和业务描述信息，当业务信息和业务描述信息相匹配，则向移动性管理实体发送事件关联信息。
S807’、AMF检测到终端不可用，下行数据通知失败，AMF向V-SMF发送响应消息(例如，Namf_CommunicationN1N2MessageTransfer)，通知DDN失败。
S808’、V-SMF进一步向V-UPF发送DDN失败指示。
S809’、当AMF确定UE不可用时(如UE处于PSM状态或者UE处于MICO状态等)，根据NEF reference ID，AMF设置或激活对应的DDN失败后终端可用事件。
S810’、终端向网络发起连接。例如，终端向网络发起TAU请求或服务请求。
S811’、AMF确定本地设置DDN失败后终端可用事件，则向NEF发送终端事件通知(例如，Namf_EventExposure_Notify)。该终端事件通知包括以下至少一个信息：终端的标识和NEF reference ID。
在本示例中，一个或多个AF订阅终端事件，AMF关联方式主要有两种：(1)AMF上是只为一个UE订阅一个availability after DDN failure的事件，然后这个事件可以有不同的NEF Reference ID，从而AMF可以通过NEF向不同的AF上报这个事件，这是一种方式。(2)另一种方式是为UE服务的每个AF可以为每个事件向AMF订阅这个availability after DDN failure事件，这样每个availability after DDN failure事件可能对应着不同的AF。
作为一种可选的方式，AMF也可以直接向AF上报这个事件。
S812’、NEF根据终端的标识和/或事件关联标识向AF发送终端事件通知(例如，Namf_EventExposure_Notify)。
AF在接收到该终端事件通知后，确定终端可用，可以重新向终端发送下行数据。根据本申请实施例提供的一种通信方法，对于管理特定业务的会话管理功能实体，向其订阅终端事件，会话管理功能实体在接收到用户面功能实体的业务检测通知时，通知接入和移动性管理功能实体监测终端事件，从而在5G架构中，可以针对特定的业务进行终端事件的订阅和监测。
上述详细阐述了本申请实施例的方法，下面提供了本申请实施例的装置。
图8为本申请实施例提供的一种通信装置的模块示意图，该通信装置可以是上述通信系统中描述的控制功能实体，具体可以是UDM，PCF或NEF等。具体地，该通信装置1000可包括：处理单元11和发送单元12；其中：
处理单元11，用于根据数据网络名称、切片信息和应用功能服务标识中的至少一个确定会话管理功能实体；
发送单元12，用于向所述会话管理功能实体发送第一消息，所述第一消息用于订阅终端事件，所述第一消息包括业务描述信息，其中，所述业务描述信息用于指示所述终端事件对应的业务。
在一个实现方式中，所述业务描述信息还用于确定为所述终端提供服务的应用功能实体。
在另一个实现方式中，所述第一消息还包括所述终端事件的事件关联标识和事件类型信息，所述事件关联标识用于标识所述终端事件和订阅所述终端事件的功能实体之间的关联关系，所述事件类型信息用于标识所述终端事件。
在又一个实现方式中，所述发送单元，还用于向接入与移动性管理功能实体发送第二消息，所述第二消息用于订阅所述终端事件，所述第二消息包括所述终端事件的事件关联标识和事件类型信息，所述事件关联标识用于标识所述终端事件和订阅所述终端事件的功能实体之间的关联关系，所述事件类型信息用于标识所述终端事件。
在又一个实现方式中，该通信装置1000还可以包括接收单元13；
所述接收单元13，用于接收来自应用功能实体的第三消息，所述第三消息用于订阅所述终端事件，所述第三消息包括所述业务描述信息。
在又一个实现方式中，所述第三消息还包括以下至少一个信息：所述终端事件对应的终端的标识、所述终端事件的事件类型信息、所述数据网络名称、所述切片信息和所述应用功能服务标识。
在又一个实现方式中，所述接收单元13，还用于接收经网络开放功能实体转发的所述第三消息。
在又一个实现方式中，所述发送单元12，还用于发送所述业务描述信息、所述事件关联标识、所述终端的标识、所述终端事件的事件类型、所述数据网络名称、所述切片信息和所述应用功能服务标识中的至少一个至统一数据库功能实体以便存储。
在又一个实现方式中，所述处理单元11，还用于从本地或统一数据库功能实体获取所述业务描述信息、所述事件关联标识、所述终端的标识、所述终端事件的事件类型信息、所述数据网络名称、所述切片信息和所述应用功能服务标识中的至少一个。
在又一个实现方式中，所述接收单元13，还用于接收来自接入和移动性管理功能实体或所述会话管理功能实体的所述终端事件通知；以及所述发送单元11，还用于发送所述终端事件通知至所述应用功能实体。
在又一个实现方式中，所述终端事件的事件类型包括下行数据通知失败后终端可用事件。
图9a为本申请实施例提供的另一种通信装置的模块示意图，该通信装置可以是上述通信系统中描述的接入与移动性管理功能实体。具体地，该通信装置2000a可包括接收单元21a、监测单元22a和发送单元23a；其中：
接收单元21a，用于接收会话管理功能实体发送的第一消息，所述第一消息用于订阅终端事件；
监测单元22a，用于监测被订阅的所述终端事件；
发送单元23a，用于当所述监测单元监测到所述终端事件时，向订阅所述终端事件的功能实体发送所述终端事件通知，其中，所述终端事件通知包括以下至少一个信息：所述终端事件对应的终端的标识和所述终端事件的事件关联标识，所述事件关联标识用于标识所述终端事件和订阅所述终端事件的功能实体之间的关联关系。
图9b为本申请实施例提供的又一种通信装置的模块示意图，该通信装置可以是上述通信系统中描述的接入与移动性管理功能实体。具体地，该通信装置2000b可包括接收单元21b、监测单元22b和发送单元23b；其中：
接收单元21b，用于接收会话管理功能实体发送的监测终端可达事件的通知；
监测单元22b，用于监测终端可达事件；
发送单元23b，用于当监测到所述终端可达事件时，向会话管理功能实体发送终端可达通知，所述终端可达通知用于下行数据通知失败后终端可用事件的监测。
图10为本申请实施例提供的又一种通信装置的模块示意图，该通信装置可以是上述通信系统中描述的会话管理功能实体。具体地，该通信装置3000可包括：发送单元31和接 收单元32；其中：
发送单元31，用于指示用户面功能实体进行业务检测，所述业务为被订阅的终端事件对应的业务，或用于向用户面功能实体发送业务信息请求；接收单元32，用于接收所述用户面功能实体发送的业务检测通知，或者业务信息，所述业务检测通知用于指示所述业务数据的发生；以及所述发送单元31还用于响应于所述业务检测通知，向接入与移动性管理功能实体发送监测所述终端事件的通知。
在一个实现方式中，所述接收单元32，还用于接收控制功能实体发送的第一消息，所述第一消息用于指示所述业务，所述第一消息包括所述业务的业务描述信息。
在另一个实现方式中，所述第一消息还用于订阅所述终端事件，所述第一消息包括所述终端事件的事件关联标识和事件类型信息，所述事件关联标识用于标识所述终端事件和订阅所述终端事件的功能实体之间的关联关系，所述事件类型信息用于标识所述终端事件。
在又一个实现方式中，所述发送单元31，用于指示所述用户面功能实体在未存储有传输所述业务数据的接入网隧道信息时，进行业务检测。
在又一个实现方式，所述终端事件包括下行数据通知失败后终端可用事件，所述接收单元32，还用于接收所述接入与移动性管理功能实体发送的终端可达通知或下行数据通知失败后终端可用事件通知；以及发送下行数据通知失败后终端可用通知至网络开放功能实体或应用功能实体。
图11为本申请实施例提供的又一种通信装置的模块示意图，该通信装置可以是上述通信系统中描述的用户面功能实体。具体地，该通信装置4000可包括：接收单元41、检测单元42和发送单元43；其中：
接收单元41，用于接收会话管理功能实体发送的第一消息或业务信息请求，所述第一消息用于指示进行业务检测，所述业务为被订阅的终端事件对应的业务；检测单元42，用于根据所述第一消息，检测所述业务；以及发送单元43，用于发送业务检测通知或业务信息至所述会话管理功能实体，所述业务检测通知用于指示所述业务数据的发生。
在一个实现方式中，所述检测单元42，用于根据所述第一消息，当未存储有传输所述业务数据的接入网隧道信息时，检测所述业务。
图12提供了本申请实施例的一种通信装置的硬件结构示意图。该通信装置包括处理器，还可以包括接收器、发射器和存储器。该接收器、发射器、存储器和处理器之间通过总线相互连接。
存储器包括但不限于是随机存储记忆体(random access memory，RAM)、只读存储器(read-only memory，ROM)、可擦除可编程只读存储器(erasable programmable read only memory，EPROM)、或便携式只读存储器(compact disc read-only memory，CD-ROM)，该存储器用于相关指令及数据。
接收器用于接收数据和/或信号，以及发射器用于发送数据和/或信号。发射器和接收器可以是独立的器件，也可以是一个整体的器件。
处理器可以包括是一个或多个处理器，例如包括一个或多个中央处理器(central processing unit，CPU)，在处理器是一个CPU的情况下，该CPU可以是单核CPU，也可以是多核CPU。
存储器用于存储网络设备的程序代码和数据。
处理器用于调用该存储器中的程序代码和数据，执行上述方法实施例中的步骤。具体可参见方法实施例中的描述，在此不再赘述。
可以理解的是，图12仅仅示出了通信装置的简化设计。在实际应用中，通信装置还可以分别包含必要的其他元件，包含但不限于任意数量的收发器、处理器、控制器、存储器等，而所有可以实现本发明实施例的通信装置都在本发明的保护范围之内。
在一个实施例中，该通信装置可以是上述通信系统中的控制功能实体。图8中的接收单元13所实现的相关功能可以由接收器来实现，发送单元12所实现的相关功能可以由发射器来实现，处理单元11所实现的相关功能可以通过一个或多个处理器来实现。
具体地，所述处理器用于根据数据网络名称、切片信息和应用功能服务标识中的至少一个确定会话管理功能实体；
所述发射器用于向所述会话管理功能实体发送第一消息，所述第一消息用于订阅终端事件，所述第一消息包括业务描述信息，其中，所述业务描述信息用于指示所述终端事件对应的业务。
在一个实现方式中，所述业务描述信息还用于确定为所述终端提供服务的应用功能实体。
在另一个实现方式中，所述第一消息还包括所述终端事件的事件关联标识和事件类型信息，所述事件关联标识用于标识所述终端事件和订阅所述终端事件的功能实体之间的关联关系，所述事件类型信息用于标识所述终端事件。
在又一个实现方式中，所述发射器还用于向接入与移动性管理功能实体发送第二消息，所述第二消息用于订阅所述终端事件，所述第二消息包括所述终端事件的事件关联标识和事件类型信息，所述事件关联标识用于标识所述终端事件和订阅所述终端事件的功能实体之间的关联关系，所述事件类型信息用于标识所述终端事件。
在又一个实现方式中，所述接收器用于接收来自应用功能实体的第三消息，所述第三消息用于订阅所述终端事件，所述第三消息包括所述业务描述信息。
在又一个实现方式中，所述第三消息还包括以下至少一个信息：所述终端事件对应的终端的标识、所述终端事件的事件类型信息、所述数据网络名称、所述切片信息和所述应用功能服务标识。
在又一个实现方式中，所述接收器还用于接收经网络开放功能实体转发的所述第三消息。
在又一个实现方式中，所述发射器还用于发送所述业务描述信息、所述事件关联标识、所述终端的标识、所述终端事件的事件类型、所述数据网络名称、所述切片信息和所述应用功能服务标识中的至少一个至统一数据库功能实体以便存储。
在又一个实现方式中，所述处理器还用于从本地或统一数据库功能实体获取所述业务描述信息、所述事件关联标识、所述终端的标识、所述终端事件的事件类型信息、所述数据网络名称、所述切片信息和所述应用功能服务标识中的至少一个。
在又一个实现方式中，所述接收器还用于接收来自接入和移动性管理功能实体或所述会话管理功能实体的所述终端事件通知；以及所述发送单元11，还用于发送所述终端事件 通知至所述应用功能实体。
在又一个实现方式中，所述终端事件的事件类型包括下行数据通知失败后终端可用事件。
在另一个实施例中，该通信装置可以是上述通信系统中的接入与移动性管理功能实体。图9a中的监测单元22a所实现的相关功能可以通过一个或多个处理器来实现，发送单元23a所实现的相关功能可以由发射器来实现，接收单元21a所实现的相关功能可以由接收器来实现。
具体地，所述接收器用于接收会话管理功能实体发送的第一消息，所述第一消息用于订阅终端事件；
所述处理器用于监测被订阅的所述终端事件；
所述发射器用于当所述监测单元监测到所述终端事件时，向订阅所述终端事件的功能实体发送所述终端事件通知，其中，所述终端事件通知包括以下至少一个信息：所述终端事件对应的终端的标识和所述终端事件的事件关联标识，所述事件关联标识用于标识所述终端事件和订阅所述终端事件的功能实体之间的关联关系。
在又一个实施例中，该通信装置可以是上述通信系统中的接入与移动性管理功能实体。图9b中的接收单元21b所实现的相关功能可以由接收器来实现，监测单元22b所实现的相关功能可以通过一个或多个处理器来实现，发送单元23b所实现的相关功能可以由发射器来实现。
具体地，该接收器用于接收会话管理功能实体发送的监测终端可达事件的通知；
该处理器用于监测终端可达事件；
该发射器用于当监测到所述终端可达事件时，向会话管理功能实体发送终端可达通知，所述终端可达通知用于下行数据通知失败后终端可用事件的监测。
在又一个实施例中，该通信装置可以是上述通信系统中的会话管理功能实体。图10中的发送单元31所实现的相关功能可以由发射器来实现，接收单元32所实现的相关功能可以由接收器来实现。
具体地，所述发射器用于指示用户面功能实体进行业务检测，所述业务为被订阅的终端事件对应的业务；
所述接收器用于接收所述用户面功能实体发送的业务检测通知，所述业务检测通知用于指示所述业务数据的发生；以及
所述发射器还用于响应于所述业务检测通知，向接入与移动性管理功能实体发送监测所述终端事件的通知。
在一个实现方式中，所述接收器还用于接收控制功能实体发送的第一消息，所述第一消息用于指示所述业务，所述第一消息包括所述业务的业务描述信息。
在另一个实现方式中，所述第一消息还用于订阅所述终端事件，所述第一消息包括所述终端事件的事件关联标识和事件类型信息，所述事件关联标识用于标识所述终端事件和订阅所述终端事件的功能实体之间的关联关系，所述事件类型信息用于标识所述终端事件。
在又一个实现方式中，所述发射器用于指示所述用户面功能实体在未存储有传输所述业务数据的接入网隧道信息时，进行业务检测。
在又一个实现方式，所述终端事件包括下行数据通知失败后终端可用事件，所述接收器还用于接收所述接入与移动性管理功能实体发送的终端可达通知或下行数据通知失败后终端可用事件通知；以及发送下行数据通知失败后终端可用通知至网络开放功能实体或应用功能实体。
在又一个实施例中，该通信装置可以是上述通信系统中的用户面功能实体。图11中的接收单元41所实现的相关功能可以由接收器来实现，检测单元42所实现的相关功能可以通过一个或多个处理器来实现，发送单元43所实现的相关功能可以由发射器来实现。
具体地，所述接收器用于接收会话管理功能实体发送的第一消息，所述第一消息用于指示进行业务检测，所述业务为被订阅的终端事件对应的业务；
所述处理器用于根据所述第一消息，检测所述业务；以及
所述发射器用于发送业务检测通知至所述会话管理功能实体，所述业务检测通知用于指示所述业务数据的发生。
在一个实现方式中，所述处理器用于根据所述第一消息，当未存储有传输所述业务数据的接入网隧道信息时，检测所述业务。
在又一个实施例中，该通信装置可以是上述通信系统中的会话管理功能实体。图15中的接收单元52所实现的相关功能可以由接收器来实现，指示单元51和监测单元53所实现的相关功能可以通过一个或多个处理器来实现，发送单元54所实现的相关功能可以由发射器来实现。
具体地，所述处理器用于指示用户面功能实体进行业务检测，所述业务为第一应用功能实体订阅的终端事件对应的业务；
所述接收器用于接收所述用户面功能实体发送的业务检测通知，所述业务检测通知用于指示检测到所述业务的数据；
所述处理器还用于当终端不可达时，根据所述业务检测通知监测所述终端事件；以及
所述发射器用于当监测到所述终端事件时，向网络开放功能实体或第一应用功能实体发送终端事件通知。
图13为本申请实施例提供的又一种通信方法的流程示意图，该方法可包括以下步骤：
S901、控制功能实体根据数据网络名称、切片信息和应用功能服务标识中的至少一个确定会话管理功能实体。
具体地，控制功能实体根据数据网络名称、切片信息和应用功能服务标识中的至少一个确定会话管理功能实体，可以是控制功能实体根据数据网络名称、或者根据切片信息、或者根据应用功能服务标识、或者根据数据网络名称和切片信息、或者根据数据网络名称和应用功能服务标识、或者根据切换信息和应用功能服务标识、或者根据数据网络名称、切片信息和应用功能服务标识，确定会话管理功能实体。
S902、该控制功能实体向该会话管理功能实体发送第一消息。该第一消息用于订阅终端事件，该第一消息包括业务描述信息，其中，该业务描述信息用于指示终端事件对应的业务。
该终端事件包括下行数据通知失败后终端可用事件或终端可达事件。
订阅终端事件用是指当发送业务数据时UE不可达或者发送业务数据失败时，进行UE 可达事件或发送数据可用事件的监测，以使得AF重新发送该业务数据。
S903、该会话管理功能实体向用户面功能实体发送第二消息。该第二消息用于指示用户面功能实体进行业务检测。该业务为被订阅的终端事件对应的业务。此外，另一种实施方式中，第二消息可以是业务信息请求，指示用户面功能实体上报业务信息，在该种情况下，则不需要进行S904。该业务信息可以是下行数据包的源IP地址，源端口号的至少一种，也可以一个索引信息，索引信息用于索引到特定的事件。该下行数据包可以为被丢弃的下行数据包。可选的，若下行数据通知失败，会话管理功能实体向用户功能实体发送业务信息请求。
可选地，SMF通过发送第二消息，来指示UPF进行业务检测。
S904、可选的，当收到的第二消息为用于指示用户面功能实体进行业务检测时，该用户面功能实体检测该业务。
S905、该用户面功能实体发送业务检测通知至会话管理功能实体。该业务检测通知用于指示业务数据的发生。会话管理功能实体接收该业务检测通知。在另一种实施方式中，该业务检测通知可以为业务信息，即在S903中的业务信息，该业务信息为根据下行数据包所确定。具体的，为根据接收到的下行数据包的包头所确定。例如，当下行数据包为IP数据包，其包头包含IP五元组信息；当下行数据包为以太数据包，其包头包含MAC地址。
S906、当终端不可达时，会话管理功能实体根据所述业务检测通知监测所述终端事件。
具体地，当接收到接入与移动性管理功能实体发送的下行数据发送失败通知，或当检测到第二应用功能实体的业务数据时，接收到接入与移动性管理功能实体发送的不可达通知，则确定所述终端不可达。
SMF根据业务检测通知监测终端事件，是指SMF在收到业务检测通知后，且UE不可达时，进行终端事件的监测。
S907、当监测到所述终端事件时，会话管理功能实体向应用功能实体发送终端事件通知。
其中，监测终端事件的可选方式为，接收所述接入与移动性管理功能实体发送的终端可达事件通知或下行数据发送失败终端可用事件通知。当接收到所述接入与移动性管理功能实体发送的终端可达事件通知或下行数据发送失败终端可用事件通知时，监测到所述终端事件。
具体地，向NEF或第一应用功能实体发送终端事件通知。
根据本申请实施例提供的一种通信方法，会话管理功能实体指示用户面功能实体检测特定的业务，在终端不可达时，根据用户面功能实体发送的业务检测通知，监测终端事件，并在监测到终端事件时，发送终端事件通知，从而可以在5G架构下，针对特定的业务进行终端事件的订阅和通知。
下面结合具体的示例对图13所示的实施例进行详细描述：
图14a为本申请实施例提供的又一种通信方法的流程示意图，该方法可包括以下步骤：
S1001、UDM/PCF根据DNN/S-NSSAI/AF-service-ID确定目标SMF。该DNN/S-NSSAI/AF-service-ID可以是从UDR获取的或者本地存储的。
S1002、UDM/PCF向目标SMF发送第一消息(例如，Nsmf_EventExposure)。该第一 消息中包含业务描述信息、事件类型信息和事件关联标识(例如，NEF reference ID)，还可以包括NEF ID等信息。在本示例中，事件类型为DDN失败后终端可用事件。
SMF接收该第一消息。
具体地，SMF在收到了availability after DDN failure事件和业务描述信息后，SMF把这两者关联到一起。这两者在一起发送(在同一个消息中发送)就代表它们是关联在一起，或者业务描述信息在availability after DDN failure事件订阅消息中发送，代表它们关联在一起。
S1003、SMF通过N4会话建立或者修改流程向UPF发送业务检测消息。该业务检测消息包括业务描述信息。
具体地，SMF在收到UPF的检测到业务描述信息对应的数据的通知时，可以确定是哪个事件对应的数据触发的事件，因此就向相应的AMF发送事件关联标识。此外，另一种实施方式中，业务检测消息可以是业务信息请求，指示用户面功能实体上报业务信息，在该种情况下，则不需要进行S1006。该业务信息可以是下行数据包的源IP地址，源端口号的至少一种，也可以一个索引信息，索引信息用于索引到特定的事件。该下行数据包可以为被丢弃的下行数据包。可选的，若下行数据通知失败，会话管理功能实体向用户功能实体发送业务信息请求。
UPF根据该业务检测消息，检测对应的业务。即检测业务描述信息对应的业务。
S1004、AMF向SMF发送UE不可达信息。
AMF可以在接收到其它AF发送的业务数据，并且检测到UE不可达时，向SMF发送UE不可达信息；或者AMF在DDN数据失败时，向SMF发送UE不可达信息。
可选地，S1004可以是在S1007之前的任一个步骤。
S1005、AF向终端发送下行数据包。
S1006、可选的，当收到的业务检测消息为用于指示用户面功能实体进行业务检测时，UPF根据包检测规则，检测到该下行数据包为被订阅的终端事件对应的业务。
当UPF中未存储该会话的接入隧道信息时，需要建立用户面隧道，UPF向SMF发送业务检测通知。该业务检测通知用于指示检测到业务数据的发生。
具体地，被订阅的终端事件对应的业务，即业务描述信息对应的业务。该包检测规则包括业务描述信息。例如，该业务描述信息为IP三元组，UPF根据该IP三元组检测接收到的下行数据包。当检测到与该IP三元组对应的下行数据包时，确认检测到业务数据的发生。
S1007、SMF在UE不可达时激活事件。
本实施例中，由SMF监测终端可达事件。
后续的流程可参考图7a所示实施例，在此不再赘述。
S1008、终端向网络发起连接。例如，终端向网络发起TAU请求或服务请求。
S1009、AMF向SMF发送UE可达事件通知。
在另一种实施方式中，该业务检测通知可以为业务信息，即在S1003中的业务信息，该业务信息为根据下行数据包所确定。具体的，为根据接收到的下行数据包的包头所确定。例如，当下行数据包为IP数据包，其包头包含IP五元组信息；当下行数据包为以太数据 包，其包头包含MAC地址。
S1010、SMF确定本地设置UE可达事件，则向NEF发送终端事件通知。该终端事件通知中包括以下至少一个信息：终端标识和事件关联标识(例如，NEF reference ID)。
S1011、NEF根据终端的标识和/或NEF reference ID向AF发送终端可用事件通知(例如，Namf_EventExposure_Notify)。
AF在接收到该终端事件通知后，确定终端可用，可以重新向终端发送下行数据。
图14b为本申请实施例提供的又一种通信方法的流程示意图，该方法可包括以下步骤：
S1101、UDM/PCF根据DNN/S-NSSAI/AF-service-ID确定目标SMF。该DNN/S-NSSAI/AF-service-ID可以从UDR获取的或者本地存储的。
S1102、UDM/PCF向目标SMF发送第一消息。
S1103、SMF通过N4会话建立或者修改流程向UPF发送业务检测消息。
S1104、AF向终端发送下行数据包。
S1105、UPF向SMF发送业务检测通知。
S1106、SMF向AMF发送第二消息。
与图14a所示实施例不同的是，这里的第二消息是正常的DDN消息，而不是事件订阅消息。其它步骤的实现可参考图14a相应的步骤描述，在此不再赘述。此外，另一种实施方式中，第二消息可以是业务信息请求，指示用户面功能实体上报业务信息。该业务信息可以是下行数据包的源IP地址，源端口号的至少一种，也可以一个索引信息，索引信息用于索引到特定的事件。该下行数据包可以为被丢弃的下行数据包。可选的，若下行数据通知失败，会话管理功能实体向用户功能实体发送业务信息请求。
S1107、AMF向SMF发送响应消息，通知UE不可达。
相应地，AMF接收到第二消息后，如果检测到UE不可达，则通知SMF UE不可达。
S1108、SMF在UE不可达时激活事件。
S1109、SMF向UPF发送下行数据通知失败消息。
S1110、AMF存储第一指示，所述第一指示用于指示SMF被通知UE不可达。
AMF存储该记录，以便在UE可达时，通知SMF。
后续的流程可参考图7a所示实施例，在此不再赘述。
S1111、终端向网络发起连接。
S1112、AMF向SMF发送UE可达事件通知。
S1113、SMF确定本地设置UE可达事件，则向NEF发送终端事件通知。
S1114、NEF根据终端的标识和/或NEF reference ID向AF发送终端可用事件通知。
AF在接收到该终端事件通知后，确定终端可用，可以重新向终端发送下行数据。
图14c为本申请实施例提供的又一种通信方法的流程示意图。该方法应用于漫游场景。该方法可包括以下步骤：
S1201、UDM/PCF确定向SMF订阅终端事件。
具体地，UDM/PCF根据DNN/S-NSSAI/AF-service-ID确定目标H-SMF。该DNN/S-NSSAI/AF-service-ID可以从UDR获取的或者本地存储的。
S1202a、UDM/PCF向目标H-SMF发送第一消息(例如，Nsmf_EventExposure)。该第一消息中包含业务描述信息、事件类型信息和事件关联标识(例如，NEF reference ID)，还可以包括NEF ID等信息。在本示例中，事件类型为DDN失败后终端可用事件。
H-SMF接收该第一消息。
S1202b、H-SMF向V-SMF转发第一消息。
V-SMF在收到了availability after DDN failure事件和业务描述信息后，V-SMF把这两者关联到一起。这两者在一起发送(在同一个消息中发送)就代表它们是关联在一起，或者业务描述信息在availability after DDN failure事件订阅消息中发送，代表它们关联在一起。
S1203、V-SMF通过N4会话建立或者修改流程向V-UPF发送业务检测消息。该业务检测消息包括业务描述信息。
具体地，V-SMF在收到V-UPF的检测到业务描述信息对应的数据的通知时，可以确定是哪个事件对应的数据触发的事件，因此就向相应的AMF发送事件关联标识。
V-UPF根据该业务检测消息，检测对应的业务。即检测业务描述信息对应的业务。
此外，另一种实施方式中，第二消息可以是业务信息请求，指示用户面功能实体上报业务信息，在该种情况下，则不需要进行S1205。该业务信息可以是下行数据包的源IP地址，源端口号的至少一种，也可以一个索引信息，索引信息用于索引到特定的事件。该下行数据包可以为被丢弃的下行数据包。可选的，若下行数据通知失败，会话管理功能实体向用户功能实体发送业务信息请求。
后续AMF检测UE是否可达等流程，可参考图7a所示实施例，在此不再赘述。
S1204、AF向终端发送下行数据包。
S1205、可选的，当收到的第二消息为用于指示用户面功能实体进行业务检测时，V-UPF根据包检测规则，检测到该下行数据包为被订阅的终端事件对应的业务。
当V-UPF中未存储该会话的接入隧道信息时，需要建立用户面隧道，V-UPF向V-SMF发送业务检测通知。该业务检测通知用于指示检测到业务数据的发生。
S1206、V-SMF在UE不可达时激活DDN失败后可用通知事件。
本实施例中，由V-SMF监测终端事件。
后续AMF检测UE可达并通知V-SMF的流程可参考图7a所示实施例，在此不再赘述。
终端向网络发起连接。
S1207、AMF向V-SMF发送第一终端事件通知。该第一终端事件通知即UE可达事件通知。
S1208a、V-SMF确定本地设置UE可达事件，则向NEF发送终端事件通知。
S1209、NEF根据终端的标识和/或NEF reference ID向AF发送终端可用事件通知(例如，Namf_EventExposure_Notify)。
作为S1208a和S1209的可替换的步骤，在S1208b中，V-SMF向AF发送终端可用事件通知。
AF在接收到该终端事件通知后，确定终端可用，可以重新向终端发送下行数据。
图14d为本申请实施例提供的又一种通信方法的流程示意图。该方法应用于漫游场景。 该方法可包括以下步骤：
S1301、UDM/PCF确定向SMF订阅终端事件。
具体地，UDM/PCF根据DNN/S-NSSAI/AF-service-ID确定目标H-SMF。该DNN/S-NSSAI/AF-service-ID可以从UDR获取的或者本地存储的。
S1302、UDM/PCF向目标H-SMF发送第一消息(例如，Nsmf_EventExposure)。该第一消息中包含业务描述信息、事件类型信息和事件关联标识(例如，NEF reference ID)，还可以包括NEF ID等信息。在本示例中，事件类型为DDN失败后终端可用事件。
H-SMF接收该第一消息。
H-SMF在收到了availability after DDN failure事件和业务描述信息后，H-SMF把这两者关联到一起。这两者在一起发送(在同一个消息中发送)就代表它们是关联在一起，或者业务描述信息在availability after DDN failure事件订阅消息中发送，代表它们关联在一起。
S1303、H-SMF通过N4会话建立或者修改流程向H-UPF发送业务检测消息。该业务检测消息包括业务描述信息。
具体地，H-SMF在收到H-UPF的检测到业务描述信息对应的数据的通知时，可以确定是哪个事件对应的数据触发的事件，因此就向相应的AMF发送事件关联标识。
H-UPF根据该业务检测消息，检测对应的业务。即检测业务描述信息对应的业务。
此外，另一种实施方式中，第二消息可以是业务信息请求，指示用户面功能实体上报业务信息，在该种情况下，则不需要进行S1306。该业务信息可以是下行数据包的源IP地址，源端口号的至少一种，也可以一个索引信息，索引信息用于索引到特定的事件。该下行数据包可以为被丢弃的下行数据包。可选的，若下行数据通知失败，会话管理功能实体向用户功能实体发送业务信息请求。
S1304、H-SMF接收UE不可达信息。
AMF可以在接收到其它AF发送的业务数据，并且检测到UE不可达时，向H-SMF发送UE不可达信息。
可选地，S1304可以是在S1307之前的任一个步骤。
S1305、AF向终端发送下行数据包。
S1306、可选的，当收到的业务检测消息为用于指示用户面功能实体进行业务检测时，H-UPF根据包检测规则，检测到该下行数据包为被订阅的终端事件对应的业务。
当H-UPF中未存储该会话的接入隧道信息时，需要建立用户面隧道，H-UPF向H-SMF发送业务检测通知。该业务检测通知用于指示检测到业务数据的发生。
S1307、H-SMF在UE不可达时激活DDN失败后可用通知事件。
本实施例中，由H-SMF监测终端事件。
后续AMF检测UE可达并通知H-SMF的流程可参考图7a所示实施例，在此不再赘述。
终端向网络发起连接。
S1308、AMF向V-SMF发送终端事件通知。该终端事件通知即UE可达事件通知。
S1309a、V-SMF向H-SMF转发所述终端事件通知。
S1309b、H-SMF确定本地设置UE可达事件，则向NEF发送终端事件通知。
S1310、NEF根据终端的标识和/或NEF reference ID向AF发送终端可用事件通知(例 如，Namf_EventExposure_Notify)。
AF在接收到该终端事件通知后，确定终端可用，可以重新向终端发送下行数据。
如图14e所示，为本申请实施例提供的又一种通信方法的流程示意图，该方法可包括以下步骤：
S1400.V-SMF从H-SMF接收事件信息或指示信息。该指示信息用于指示V-SMF在接收到AMF发送的会话去激活信息时，向V-UPF发送N4会话释放请求。
S1401a.UE与(R)AN进行连接释放(connection release)流程。
S1401b.(R)AN向AMF发送UE上下文释放请求(UE context release request)。
S1402.AMF向(R)AN发送UE上下文释放命令(UE context release command)。
S1403.(R)AN与UE完成连接释放流程。
S1404.(R)AN向AMF发送UE上下文释放完成(UE context release complete)消息。
S1405.AMF向V-SMF发送会话更新会话上下文(PDU session_update SM contex)消息。
S1406.V-SMF基于指示信息删除V-UPF的N4会话，并通知H-SMF修改A-UPF的N4会话。在上述实施例中，V-SMF获得了事件监测信息，可基于该事件监测信息对会话进行管理。
具体地，包括以下步骤：
S1406a.V-SMF向V-UPF发送会话释放请求(N4 session release request)。
S1406’a.V-SMF向H-SMF发送会话更新请求(PDU session update request)。
S1406b.V-UPF向V-SMF发送会话释放响应(N4 session release response)。
S1406’b.H-SMF向V-SMF发送会话更新响应(PDU session update response)。
S1407.V-SMF向AMF发送会话更新会话管理上下文响应(PDU session update SM context ACK)。
如图14f所示，为本申请实施例提供的又一种通信方法的流程示意图，可应用于多个UPF的场景。例如，本实施例中，A-UPF管理一个中间用户面功能实体(I-UPF)。该方法可包括以下步骤：
S1501a.UE与(R)AN进行连接释放(connection release)流程。
S1501b.(R)AN向AMF发送UE上下文释放请求(UE context release request)。
S1502.AMF向(R)AN发送UE上下文释放命令(UE context release command)。
S1503.(R)AN与UE完成连接释放流程。
S1504.(R)AN向AMF发送UE上下文释放完成(UE context release complete)消息。
S1505.AMF向SMF发送会话更新会话上下文(PDU session_update SM contex)消息。
S1506.SMF基于事件监测信息删除I-UPF的N4会话，并修改A-UPF的N4会话。在上述实施例中，SMF获得了事件监测信息，可基于该事件监测信息对会话进行管理。该N4会话为业务描述信息对应的会话。
具体地，包括以下步骤：
S1506a.SMF向I-UPF发送会话释放请求(N4 session release request)。
S1506’a.SMF向A-UPF发送会话修改请求(N4 session modification request)。
S1506b.I-UPF向SMF发送会话释放响应(N4 session release response)。
S1506’b.A-UPF向SMF发送会话修改响应(N4 session modification response)。
S1507.SMF向AMF发送会话更新会话管理上下文响应(PDU session update SM context ACK)。
图15为本申请实施例提供的又一种通信装置的结构示意图，该装置5000可包括：
指示单元51，用于指示用户面功能实体进行业务检测，所述业务为第一应用功能实体订阅的终端事件对应的业务。
接收单元52，用于接收所述用户面功能实体发送的业务检测通知，所述业务检测通知用于指示检测到所述业务的数据。
监测单元53，用于当终端不可达时，根据所述业务检测通知监测所述终端事件。
发送单元54，用于当监测到所述终端事件时，向网络开放功能实体或第一应用功能实体发送终端事件通知。
在第一种可能的实现方式中，所述终端事件包括下行数据通知失败后终端可用事件或终端可达事件。
在第二种可能的实现方式中，所述监测所述终端事件为接收到所述接入与移动性管理功能实体发送的终端可达事件通知或下行数据发送失败终端可用事件通知。
在第三种可能的实现方式中，所述装置还包括：确定单元，用于当接收到接入与移动性管理功能实体发送的下行数据发送失败通知，或当检测到第二应用功能实体的业务数据时，接收到接入与移动性管理功能实体发送的不可达通知，则确定所述终端不可达。
在第四种可能的实现方式中，所述接收单元52还用于接收本地会话管理功能实体发送的第一消息，所述第一消息用于指示所述业务和订阅所述终端事件，所述第一消息包括所述业务的业务描述信息，所述终端事件的事件关联标识和事件类型信息，所述事件关联标识用于标识所述终端事件和订阅所述终端事件的功能实体之间的关联关系，所述事件类型信息用于标识所述终端事件。
有关上述指示单元51、接收单元52、监测单元53和发送单元54的具体实现可参考图13～图14f所示的实施例。
图16为本申请实施例提供的又一种通信方法的流程示意图，其中：
S1601、控制功能实体向AMF发送终端事件的第一消息。
在UE注册到网络的流程中或者UE注册到网络之后，UDM/PCF确定向AMF订阅事件。UDM/PCF确定向AMF订阅事件。其中，所述第一消息用于订阅终端事件，所述第一消息包括业务描述信息和DNN/S-NSSAI。该第一消息还可以包括事件类型，NEF ID，NEF reference ID。
S1602、AMF接收到上述第一消息后，AMF向SMF发送第二消息。
其中，该第二消息用于订阅业务检测事件，该第二消息包括上述业务描述信息。该第二消息还可以包括事件类型，NEF ID，NEF reference ID；或者包括事件类型，AMF ID，AMF reference ID。其中，AMF reference ID为AMF生成的，用于关联对应的事件或者事件上报。
在一个实现中，AMF判断已经建立的PDU会话或者正在建立的PDU会话的DNN/S-NSSAI与第一消息中包括的DNN/S-NSSAI是否相同，当相同时，AMF向SMF发 送上述第二消息。
在又一个实现中，S1602具体包括：向本地会话管理功能实体或漫游地会话管理功能实体发送订阅请求；或
向本地会话管理功能实体或漫游地会话管理功能实体发送会话上下文更新请求，所述会话上下文更新请求用于订阅所述终端事件。
S1603、SMF接收到上述第二消息后，SMF向UPF发送第三消息。
其中，该第三消息用于指示进行业务检测，所述业务为被订阅的终端事件对应的业务。
在一个实现中，S1603包括：在PDU会话去激活过程中或之后，向用户面功能实体发送所述第三消息，所述第三消息用于指示进行业务检测，所述业务为被订阅的终端事件对应的业务。具体地，SMF通过N4会话建立或者修改流程或者新的N4消息向UPF订阅业务检测事件。
此外，另一种实施方式中，第三消息可以是业务信息请求，指示用户面功能实体上报业务信息，在该种情况下，则不需要进行S1604。该业务信息可以是下行数据包的源IP地址，源端口号的至少一种，也可以一个索引信息，索引信息用于索引到特定的事件。该下行数据包可以为被丢弃的下行数据包。可选的，若下行数据通知失败，会话管理功能实体向用户功能实体发送业务信息请求。
S1604、可选的，当收到的第三消息为用于指示用户面功能实体进行业务检测时，UPF接收到上述第三消息，且检测到业务数据时，UPF向SMF发送业务检测通知。
其中，该业务检测通知用于指示业务数据的发生。在另一种实施方式中，该业务检测通知可以为业务信息，即在S1603中的业务信息，该业务信息为根据下行数据包所确定。具体的，为根据接收到的下行数据包的包头所确定。例如，当下行数据包为IP数据包，其包头包含IP五元组信息；当下行数据包为以太数据包，其包头包含MAC地址。
S1605、SMF接收到上述业务检测通知后，SMF向AMF发送上述业务检测通知。
该业务检测通知携带reference ID，用于索引到特定的事件。其中，reference ID为AMF生成或者NEF生成的。若为NEF生成时，可选的包括NEF ID，以防止不同的NEF可能会生成相同的reference ID而无法唯一识别特定的事件。可选的，该监测终端事件的通知可以包含事件关联信息，如NEF Reference ID。该事件关联信息用于确定事件上报信息。可选的，会话管理功能实体根据业务描述信息和业务信息，向移动性管理实体发送事件关联信息，即通过比较业务信息和业务描述信息，当业务信息和业务描述信息相匹配，则向移动性管理实体发送事件关联信息。
S1606、AMF接收到上述业务检测通知后，检测UE是否可达。当UE不可达时，激活上述终端事件。
S1607、当AMF检测到UE可达时，向能力开放节点或应用功能实体发送终端事件通知。
根据本申请实施例提供的一种通信方法，控制功能实体可以向AMF进行终端事件订阅，当AMF接收到业务检测通知，且检测到终端不可达时，激活终端事件。并在AMF检测到终端可达时，向能力开放节点或应用功能实体发送终端事件通知，从而可以在5G架构下，针对特定的业务进行终端事件的订阅。
下面结合具体的场景对上述通信方法进行完整、详细的描述：
针对LBO或者非漫游场景，图17提供了本申请实施例的又一种通信方法的流程示意图，其中：
S1701、在UE注册到网络的流程中或者UE注册到网络之后，UDM/PCF确定向AMF订阅事件。
S1702a、UDM/PCF(AMF-PCF)向AMF发送订阅请求消息(Namf_EventExposure)，该消息中包括事件类型，NEF ID，NEF reference ID，DNN/S-NSSAI，业务描述信息。
S1702b、AMF向UDM/PCF发送Namf_EventExposure响应消息。
S1703、AMF根据DNN/S-NSSAI确定向SMF订阅事件，AMF判断已经建立的PDU会话或者正在建立的PDU会话的DNN/S-NSSAI和事件的DNN/S-NSSAI是否相同。
S1704a、AMF向SMF发送Nsmf_EventExposure请求，请求消息中包括事件类型，业务描述、NEF ID，NEF reference ID。或者包括事件类型，业务描述、AMF ID，AMF reference ID。其中，AMF reference ID为AMF生成的，用于关联对应的事件或者事件上报。
S1704b、SMF向AMF发送Nsmf_EventExposure响应。
S1705、SMF通过N4会话建立或者修改流程或者新的N4消息向UPF订阅业务检测事件。
在一种实施方式中，该消息可以是业务信息请求，指示用户面功能实体上报业务信息，在该种情况下，则不需要进行S1706。该业务信息可以是下行数据包的源IP地址，源端口号的至少一种，也可以一个索引信息，索引信息用于索引到特定的事件。该下行数据包可以为被丢弃的下行数据包。可选的，若下行数据通知失败，会话管理功能实体向用户功能实体发送业务信息请求。
S1706、可选的，当收到的消息为用于指示用户面功能实体进行业务检测时，UPF接收AF发送的数据包。
S1707、UPF确定为上述特定的业务，则向SMF发送业务检测上报。
在另一种实施方式中，该业务检测上报可以为业务信息，即在S1703中的业务信息，该业务信息为根据下行数据包所确定。具体的，为根据接收到的下行数据包的包头所确定。例如，当下行数据包为IP数据包，其包头包含IP五元组信息；当下行数据包为以太数据包，其包头包含MAC地址。
S1708、SMF向AMF发送Nsmf_EventExposureNotify，消息中携带reference ID，用于索引到特定的事件。其中，reference ID为AMF生成或者NEF生成的。若为NEF生成时，可选的包括NEF ID，以防止不同的NEF可能会生成相同的reference ID而无法唯一识别特定的事件。可选的，该监测终端事件的通知可以包含事件关联信息，如事件关联标识(NEF Reference ID)。该事件关联信息用于确定事件上报信息。可选的，会话管理功能实体根据业务描述信息和业务信息，向移动性管理实体发送事件关联信息，即通过比较业务信息和业务描述信息，当业务信息和业务描述信息相匹配，则向移动性管理实体发送事件关联信息。
S1709、若UE不可达，则AMF激活特定的事件。
S1710、UE向网络发起连接。
S1711、UE进入可达状态，AMF向NEF上报UE可达事件。
S1712、NEF进一步的通知AF所述UE可达。
针对HR场景，图18提供了本申请实施例的又一种通信方法的流程示意图，其中：
S1801、在UE注册到网络的流程中或者UE注册到网络之后，UDM/PCF确定向AMF订阅事件。
S1802a、UDM/PCF(AMF-PCF)向AMF发送Namf_EventExposure请求消息，消息中包括事件类型，NEF ID，NEF reference ID，DNN/S-NSSAI，业务描述信息。
S1802b、AMF向UDM/PCF发送Namf_EventExposure响应消息。
S1803、AMF根据DNN/S-NSSAI确定向H-SMF订阅事件，AMF判断已经建立的PDU会话或者正在建立的PDU会话的DNN/S-NSSAI和事件的DNN/S-NSSAI是否相同。
S1804a、AMF向H-SMF发送Nsmf_EventExposure请求，请求消息中包括事件类型，业务描述、NEF ID，NEF reference ID。或者包括事件类型，业务描述、AMF ID，AMF reference ID。其中，AMF reference ID为AMF生成的，用于关联对应的事件或者事件上报。
此外，另一种实施方式中，该订阅请求消息可以是业务信息请求，指示用户面功能实体上报业务信息，在该种情况下，则不需要进行S1806。该业务信息可以是下行数据包的源IP地址，源端口号的至少一种，也可以一个索引信息，索引信息用于索引到特定的事件。该下行数据包可以为被丢弃的下行数据包。可选的，若下行数据通知失败，会话管理功能实体向用户功能实体发送业务信息请求。
S1804b、H-SMF向AMF发送Nsmf_EventExposure响应。可选的，AMF通过V-SMF向H-SMF订阅事件。AMF向V-SMF发送事件订阅信息，进一步的V-SMF向H-SMF发送事件订阅信息。
S1805、H-SMF通过N4会话建立或者修改流程或者新的N4消息向H-UPF订阅业务检测事件。
S1806、可选的，当收到的订阅请求消息为用于指示用户面功能实体进行业务检测时，H-UPF接收AF发送的数据包。
S1807、H-UPF确定为上述特定的业务，则向H-SMF发送业务检测上报。在另一种实施方式中，该业务检测上报可以为业务信息，即在S1803中的业务信息，该业务信息为根据下行数据包所确定。具体的，为根据接收到的下行数据包的包头所确定。例如，当下行数据包为IP数据包，其包头包含IP五元组信息；当下行数据包为以太数据包，其包头包含MAC地址。
S1808、H-SMF向AMF发送Nsmf_EventExposureNotify，消息中携带reference ID，用于索引到特定的事件。其中，reference ID为AMF生成或者NEF生成的。若为NEF生成时，可选的包括NEF ID，以防止不同的NEF可能会生成相同的reference ID而无法唯一识别特定的事件。可选的，H-SMF向V-SMF发送的事件通知，以便V-SMF向AMF发送事件通知。
可选的，该监测终端事件的通知可以包含事件关联信息，如事件关联标识(NEF Reference ID)。该事件关联信息用于确定事件上报信息。可选的，会话管理功能实体根据业务描述信息和业务信息，向移动性管理实体发送事件关联信息，即通过比较业务信息和 业务描述信息，当业务信息和业务描述信息相匹配，则向移动性管理实体发送事件关联信息。
S1809、若UE不可达，则AMF激活特定的事件。
S1810、UE向网络发起连接。
S1811、UE进入可达状态，AMF向NEF上报UE可达事件。
S1812、NEF进一步的通知AF所述UE可达。
针对LBO或者非漫游场景，图19提供了本申请实施例的又一种通信方法的流程示意图，其中：
S1901、在UE注册到网络的流程中或者UE注册到网络之后，UDM/PCF确定向AMF订阅事件。
S1902a、UDM/PCF(AMF-PCF)向AMF发送Namf_EventExposure请求消息，消息中包括事件类型，NEF ID，NEF reference ID，DNN/S-NSSAI，业务描述信息。
S1902b、AMF向UDM/PCF发送Namf_EventExposure响应消息。
S1903、AMF根据DNN/S-NSSAI确定向SMF发送事件，AMF判断已经建立的PDU会话或者正在建立的PDU会话的DNN/S-NSSAI和事件的DNN/S-NSSAI是否相同。
S1904a、AMF向SMF发送Nsmf_PDUSession_UpdateSMContext请求，请求消息中包括业务描述、NEF ID，NEF reference ID。或者包含业务描述、AMF ID，AMF reference ID。其中，AMF reference ID为AMF生成的，用于关联对应的事件或者事件上报。
S1904b、SMF向AMF发送Nsmf_PDUSession_UpdateSMContext响应。
S1905、SMF通过N4会话建立或者修改流程或者新的N4消息向UPF发送业务检测信息。进一步可选的，SMF在PDU会话去激活的过程中向UPF发送业务信息，所述UPF为N3接口对应的UPF。此外，另一种实施方式中，订阅请求消息可以是业务信息请求，指示用户面功能实体上报业务信息，在该种情况下，则不需要进行S1906。该业务信息可以是下行数据包的源IP地址，源端口号的至少一种，也可以一个索引信息，索引信息用于索引到特定的事件。该下行数据包可以为被丢弃的下行数据包。可选的，若下行数据通知失败，会话管理功能实体向用户功能实体发送业务信息请求。
S1906、可选的，当收到的订阅请求消息为用于指示用户面功能实体进行业务检测时，UPF接收AF发送的数据包。
S1907、UPF确定为上述特定的业务，则通过DN消息向SMF发送业务通知。在另一种实施方式中，该业务通知可以为业务信息，即在S1903中的业务信息，该业务信息为根据下行数据包所确定。具体的，为根据接收到的下行数据包的包头所确定。例如，当下行数据包为IP数据包，其包头包含IP五元组信息；当下行数据包为以太数据包，其包头包含MAC地址。
S1908a、SMF向AMF发送Namf_Communication_N1N2Message，消息中携带reference ID,用于索引到特定的事件。其中，reference ID为AMF生成或者NEF生成的。若为NEF生成时，可选的包括NEF ID，以防止不同的NEF可能会生成相同的reference ID而无法唯一识别特定的事件。
可选的，该监测终端事件的通知可以包含事件关联信息，如事件关联标识(NEF  Reference ID)。该事件关联信息用于确定事件上报信息。可选的，会话管理功能实体根据业务描述信息和业务信息，向移动性管理实体发送事件关联信息，即通过比较业务信息和业务描述信息，当业务信息和业务描述信息相匹配，则向移动性管理实体发送事件关联信息。
S1908b、AMF向SMF发送Namf_Communication_N1N2Message响应。
S1909、若UE不可达，则AMF激活特定的事件。
S1910、UE向网络发起连接。
S1911、UE进入可达状态，AMF向NEF上报UE可达事件。
S1912、NEF进一步的通知AF所述UE可达。
针对HR场景，图20提供了本申请实施例的又一种通信方法的流程示意图，其中：
S2001、在UE注册到网络的流程中或者UE注册到网络之后，UDM/PCF确定向AMF订阅事件。
S2002a、UDM/PCF(AMF-PCF)向AMF发送Namf_EventExposure请求消息，消息中包括事件类型，NEF ID，NEF reference ID，DNN/S-NSSAI，业务描述信息。
S2002b、AMF向UDM/PCF发送Namf_EventExposure响应消息。
S2003、AMF根据DNN/S-NSSAI确定向SMF发送事件，AMF判断已经建立的PDU会话或者正在建立的PDU会话的DNN/S-NSSAI和事件的DNN/S-NSSAI是否相同。
S2004a、AMF向V-SMF发送Nsmf_PDUSession_UpdateSMContext请求，请求消息中包括业务描述、NEF ID，NEF reference ID。或者包括业务描述、AMF ID，AMF reference ID。其中，AMF reference ID为AMF生成的，用于关联对应的事件或者事件上报。
S2004b、V-SMF向AMF发送Nsmf_PDUSession_UpdateSMContext响应。
S2005、V-SMF通过N4会话建立或者修改流程或者新的N4消息向UPF发送业务检测信息。进一步可选的，V-SMF在PDU会话去激活的过程中向UPF发送业务信息，所述UPF为终结N3接口的UPF或者N9接口的UPF。此外，另一种实施方式中，第二消息可以是业务信息请求，指示用户面功能实体上报业务信息，在该种情况下，则不需要进行S2006。该业务信息可以是下行数据包的源IP地址，源端口号的至少一种，也可以一个索引信息，索引信息用于索引到特定的事件。该下行数据包可以为被丢弃的下行数据包。可选的，若下行数据通知失败，会话管理功能实体向用户功能实体发送业务信息请求。
S2006、可选的，当收到的订阅请求消息为用于指示用户面功能实体进行业务检测时，V-UPF接收AF发送的数据包。
S2007、在没有下行隧道时，V-UPF确定为上述特定的业务，则通过DN消息向V-SMF发送业务通知。在另一种实施方式中，该业务通知可以为业务信息，即在S2003中的业务信息，该业务信息为根据下行数据包所确定。具体的，为根据接收到的下行数据包的包头所确定。例如，当下行数据包为IP数据包，其包头包含IP五元组信息；当下行数据包为以太数据包，其包头包含MAC地址。
S2008a、V-SMF向AMF发送Namf_Communication_N1N2Message，消息中携带reference ID,用于索引到特定的事件。其中，所述reference ID为AMF生成或者NEF生成的。若为NEF生成时，可选的包括NEF ID，以防止不同的NEF可能会生成相同的reference ID，而 无法唯一识别特定的事件。可选的，该监测终端事件的通知可以包含事件关联信息，如事件关联标识(NEF Reference ID)。该事件关联信息用于确定事件上报信息。可选的，会话管理功能实体根据业务描述信息和业务信息，向移动性管理实体发送事件关联信息，即通过比较业务信息和业务描述信息，当业务信息和业务描述信息相匹配，则向移动性管理实体发送事件关联信息。
S2008b、AMF向V-SMF发送Namf_Communication_N1N2Message响应。
S2009、若UE不可达，则AMF激活特定的事件。
S2010、UE向网络发起连接。
S2011、UE进入可达状态，AMF向NEF上报UE可达事件。
S2012、NEF进一步的通知AF所述UE可达。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者通过所述计算机可读存储介质进行传输。所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，数字通用光盘(digital versatile disc，DVD))、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，该流程可以由计算机程序来指令相关的硬件完成，该程序可存储于计算机可读取存储介质中，该程序在执行时，可包括如上述各方法实施例的流程。而前述的存储介质包括：只读存储器(read-only memory，ROM)或随机存储存储器(random access memory，RAM)、磁碟或者光盘等各种可存储程序代码的介质。

Claims (52)

  1. 一种通信方法，其特征在于，包括：
    根据数据网络名称、切片信息和应用功能服务标识中的至少一个确定会话管理功能实体；
    向所述会话管理功能实体发送第一消息，所述第一消息用于订阅终端事件，所述第一消息包括业务描述信息，其中，所述业务描述信息用于指示所述终端事件对应的业务。
  2. 如权利要求1所述的方法，其特征在于，所述业务描述信息还用于确定为所述终端提供服务的应用功能实体。
  3. 如权利要求1或2所述的方法，其特征在于，所述第一消息还包括所述终端事件的事件关联标识和事件类型信息，所述事件关联标识用于确定事件上报信息，所述事件类型信息用于标识所述终端事件。
  4. 如权利要求1或2所述的方法，其特征在于，还包括：向接入与移动性管理功能实体发送第二消息，所述第二消息用于订阅所述终端事件，所述第二消息包括所述终端事件的事件关联标识和事件类型信息，所述事件关联标识用于确定事件上报信息，所述事件类型信息用于标识所述终端事件。
  5. 如权利要求1或2所述的方法，其特征在于，所述第一消息还包括所述终端事件的事件关联标识和事件类型信息，所述事件关联标识用于标识所述终端事件和订阅所述终端事件的功能实体之间的关联关系，所述事件类型信息用于标识所述终端事件。
  6. 如权利要求1或2所述的方法，其特征在于，还包括：向接入与移动性管理功能实体发送第二消息，所述第二消息用于订阅所述终端事件，所述第二消息包括所述终端事件的事件关联标识和事件类型信息，所述事件关联标识用于标识所述终端事件和订阅所述终端事件的功能实体之间的关联关系，所述事件类型信息用于标识所述终端事件。
  7. 如权利要求1～6任一项所述的方法，其特征在于，还包括：
    接收来自应用功能实体所述业务描述信息。
  8. 如权利要求7所述的方法，其特征在于，还包括：
    发送所述业务描述信息、所述事件关联标识或所述终端事件的事件类型中的至少一个至统一数据库功能实体以便存储。
  9. 如权利要求1～8任一项所述的方法，其特征在于，还包括：
    从本地或统一数据库功能实体获取所述业务描述信息、所述事件关联标识或所述终端事件的事件类型信息中的至少一个。
  10. 如权利要求7～9任一项所述的方法，其特征在于，还包括：
    接收来自接入和移动性管理功能实体或所述会话管理功能实体的所述终端事件通知；
    发送所述终端事件通知至所述应用功能实体。
  11. 如权利要求1～10任一项所述的方法，其特征在于，所述终端事件的事件类型包括下行数据通知失败后终端可用事件。
  12. 一种通信方法，其特征在于，包括：
    接收会话管理功能实体发送的第一消息，所述第一消息用于订阅终端事件；
    监测被订阅的所述终端事件；
    当监测到所述终端事件时，向订阅所述终端事件的功能实体发送终端事件通知，其中，所述终端事件通知包括以下至少一个信息：所述终端事件对应的终端的标识和所述终端事件的事件关联标识，所述事件关联标识用于标识所述终端事件和订阅所述终端事件的功能实体之间的关联关系。
  13. 一种通信方法，其特征在于，包括：
    接收会话管理功能实体或者控制功能实体发送的监测终端可达事件的通知；
    监测终端可达事件；
    当监测到所述终端可达事件时，向会话管理功能实体或者控制功能实体发送终端可达通知，所述终端可达通知用于下行数据通知失败后终端可用事件的监测。
  14. 一种通信方法，其特征在于，包括：
    指示用户面功能实体进行业务检测，所述业务为被订阅的终端事件对应的业务；
    接收所述用户面功能实体发送的业务检测通知，所述业务检测通知用于指示所述业务数据的发生；
    响应于所述业务检测通知，向接入与移动性管理功能实体或者控制功能实体发送监测所述终端事件的通知。
  15. 如权利要求14所述的方法，其特征在于，所述指示用户面功能实体进行业务检测，包括：
    指示所述用户面功能实体在未存储有传输所述业务数据的接入网隧道信息或者下行用户面隧道信息时，进行业务检测；或者
    指示所述用户面功能实体在未存储有传输所述业务数据的接入网隧道信息或者下行用户面隧道信息时，进行业务检测通知。
  16. 如权利要求14或15所述的方法，其特征在于，还包括：
    接收控制功能实体发送的第一消息，所述第一消息用于指示所述业务，所述第一消息包括所述业务的业务描述信息。
  17. 如权利要求14或15所述的方法，其特征在于，还包括：
    接收本地会话管理功能实体发送的第一消息，所述第一消息用于指示所述业务，所述第一消息包括所述业务的业务描述信息。
  18. 如权利要求16或17所述的方法，其特征在于，所述第一消息还用于订阅所述终端事件，所述第一消息包括所述终端事件的事件关联标识和事件类型信息，所述事件关联标识用于标识所述终端事件和订阅所述终端事件的功能实体之间的关联关系，所述事件类型信息用于标识所述终端事件。
  19. 如权利要求18所述的方法，其特征在于，所述终端事件包括下行数据通知失败后终端可用事件，所述方法还包括：
    接收所述接入与移动性管理功能实体发送的终端可达通知或下行数据通知失败后终端可用事件通知；
    发送下行数据通知失败后终端可用通知至网络开放功能实体或应用功能实体。
  20. 一种通信方法，其特征在于，包括：
    指示用户面功能实体进行业务检测，所述业务为第一应用功能实体订阅的终端事件对应的业务；
    接收所述用户面功能实体发送的业务检测通知，所述业务检测通知用于指示检测到所述业务的数据；
    当终端不可达时，根据所述业务检测通知监测所述终端事件；
    当监测到所述终端事件时，向网络开放功能实体或第一应用功能实体发送终端事件通知。
  21. 如权利要求20所述的方法，其特征在于，所述终端事件包括下行数据通知失败后终端可用事件或终端可达事件。
  22. 如权利要求21所述的方法，其特征在于，所述监测到所述终端事件，包括：
    接收到所述接入与移动性管理功能实体发送的终端可达事件通知或下行数据发送失败终端可用事件通知。
  23. 如权利要求20～22任一项所述的方法，其特征在于，所述方法还包括：当接收到接入与移动性管理功能实体发送的下行数据发送失败通知，或检测到所述业务之前，接收到接入与移动性管理功能实体发送的不可达通知，则确定所述终端不可达。
  24. 如权利要求23所述的方法，其特征在于，所述方法还包括：
    接收本地会话管理功能实体发送的第一消息，所述第一消息用于指示所述业务和订阅所述终端事件，所述第一消息包括所述业务的业务描述信息，所述终端事件的事件关联标识和事件类型信息，所述事件关联标识用于标识所述终端事件和订阅所述终端事件的功能实体之间的关联关系，所述事件类型信息用于标识所述终端事件。
  25. 一种通信方法，其特征在于，包括：
    接收会话管理功能实体发送的第一消息，所述第一消息用于指示进行业务检测，所述业务为被订阅的终端事件对应的业务；
    根据所述第一消息，检测所述业务；
    发送业务检测通知至所述会话管理功能实体，所述业务检测通知用于指示所述业务数据的发生。
  26. 如权利要求25所述的方法，其特征在于，所述根据所述第一消息，检测所述业务，包括：
    根据所述第一消息，当未存储有传输所述业务数据的接入网隧道信息时，检测所述业务。
  27. 一种通信方法，其特征在于，包括：
    接收控制功能实体发送的终端事件的第一消息，其中，所述第一消息用于订阅终端事件，所述第一消息包括业务描述信息和数据网络名称/单网络切片选择辅助信息DNN/S-NSSAI；
    向会话管理功能实体发送第二消息，其中，所述第二消息用于订阅业务检测事件，所述第二消息包括所述业务描述信息；
    接收来自所述会话管理功能实体的业务检测通知；
    当终端不可达时，激活所述终端事件；
    当检测到所述终端可达时，向能力开放节点或者应用功能实体发送终端可达通知。
  28. 根据权利要求27所述的方法，其特征在于，所述向会话管理功能实体发送第二消息，包括：
    当会话的DNN/S-NSSAI与所述第一消息中包括的DNN/S-NSSAI相同时，向所述会话管理功能实体发送所述第二消息。
  29. 根据权利要求27或28所述的方法，其特征在于，所述向会话管理功能实体发送第二消息，包括：
    向本地会话管理功能实体或漫游地会话管理功能实体发送订阅请求；或
    向本地会话管理功能实体或漫游地会话管理功能实体发送会话上下文更新请求，所述会话上下文更新请求用于订阅所述终端事件。
  30. 一种通信方法，其特征在于，包括：
    接收来自移动性管理功能实体AMF的终端事件的第二消息；
    向用户面功能实体UPF发送第三消息，所述第三消息用于指示进行业务检测，所述业务为被订阅的终端事件对应的业务；
    接收来自所述用户面功能实体的业务检测通知，所述业务检测通知用于指示所述业务数据的发生；
    向所述移动性管理功能实体发送所述业务检测通知。
  31. 根据权利要求30所述的方法，其特征在于，所述接收来自移动性管理功能实体的终端事件的第二消息，包括：
    接收来自所述移动性管理功能实体的会话上下文更新请求，所述会话上下文更新请求用于订阅所述终端事件。
  32. 根据权利要求30所述的方法，其特征在于，向用户面功能实体发送第三消息，包括：
    在PDU会话去激活过程中或之后，向用户面功能实体发送所述第三消息，所述第三消息用于指示进行业务检测，所述业务为被订阅的终端事件对应的业务。
  33. 一种通信方法，其特征在于，包括：
    接收来自控制功能实体的第一消息，所述第一消息用于订阅终端事件，所述第一消息包括业务描述信息，其中，所述业务描述信息用于指示所述终端事件对应的业务；
    接收来自用户功能实体UPF的业务信息，所述业务信息为根据下行数据包所确定；
    至少根据所述业务信息，向移动性管理实体或者能力开放实体发送事件关联信息，所述事件关联信息用于确定事件上报信息。
  34. 根据权利要求33所述的方法，其特征在于，所述接收用户功能实体的业务信息之前，包括：
    向用户功能实体发送业务信息请求。
  35. 根据权利要求34所述的方法，其特征在于，所述向用户功能实体发送业务信息请求，包括：
    当接收到用户设备UE不可达信息，向所述用户功能实体发送所述业务信息请求。
  36. 根据权利要求34所述的方法，其特征在于，所述向用户功能实体发送业务信息请求，包括：
    若下行数据通知失败，向所述用户功能实体发送所述业务信息请求。
  37. 根据权利要求33所述的方法，其特征在于，向移动性管理实体或者能力开放实体发送事件关联信息，所述事件关联信息用于确定事件上报信息，包括：
    根据所述业务描述信息和所述业务信息，向移动性管理实体或者能力开放实体发送事件关联信息，所述事件关联信息用于确定事件上报信息。
  38. 一种通信装置，其特征在于，包括处理器，所述处理器用于与存储器耦合，读取并执行所述存储器中的指令，以实现如权利要求1～11任一项所述的方法。
  39. 根据权利要求35所述的装置，其特征在于，还包括：
    所述存储器。
  40. 一种通信装置，其特征在于，包括处理器，所述处理器用于与存储器耦合，读取并执行所述存储器中的指令，以实现如权利要求12或13所述的方法。
  41. 根据权利要求27所述的装置，其特征在于，还包括：
    所述存储器。
  42. 一种通信装置，其特征在于，包括处理器，所述处理器用于与存储器耦合，读取并执行所述存储器中的指令，以实现如权利要求14～19任一项所述的方法。
  43. 根据权利要求29所述的装置，其特征在于，还包括：
    所述存储器。
  44. 一种通信装置，其特征在于，包括处理器，所述处理器用于与存储器耦合，读取并执行所述存储器中的指令，以实现如权利要求20～24任一项所述的方法。
  45. 根据权利要求31所述的装置，其特征在于，还包括：
    所述存储器。
  46. 一种通信装置，其特征在于，包括处理器，所述处理器用于与存储器耦合，读取并执行所述存储器中的指令，以实现如权利要求25或26所述的方法。
  47. 根据权利要求33所述的装置，其特征在于，还包括：
    所述存储器。
  48. 一种通信装置，其特征在于，包括处理器，所述处理器用于与存储器耦合，读取并执行所述存储器中的指令，以实现如权利要求27～29、或权利要求30～32、或权利要求33～37任一项所述的方法。
  49. 根据权利要求48所述的装置，其特征在于，还包括：
    所述存储器。
  50. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行权利要求1～34任一项所述的方法。
  51. 一种通信系统，其特征在于，所述通信系统包括如权利要求48或49所述的通信装置。
  52. 根据权利要求50所述的通信系统，其特征在于，所述通信系统还包括如权利要求38或39所述的通信装置。
PCT/CN2019/081974 2018-04-09 2019-04-09 通信方法及装置 WO2019196846A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
KR1020207031097A KR102486370B1 (ko) 2018-04-09 2019-04-09 통신 방법 및 장치
BR112020020740-3A BR112020020740A2 (pt) 2018-04-09 2019-04-09 Método e aparelho de comunicações
EP19785700.6A EP3764672A4 (en) 2018-04-09 2019-04-09 COMMUNICATION PROCESS AND DEVICE
US17/067,377 US11523268B2 (en) 2018-04-09 2020-10-09 Communications method and apparatus
US17/983,019 US20230056728A1 (en) 2018-04-09 2022-11-08 Communications Method and Apparatus

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
CN201810313171.8 2018-04-09
CN201810313171 2018-04-09
CN201811378685 2018-11-19
CN201811378685.8 2018-11-19
CN201910120722.3A CN109951824B (zh) 2018-04-09 2019-02-18 通信方法及装置
CN201910120722.3 2019-02-18

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/067,377 Continuation US11523268B2 (en) 2018-04-09 2020-10-09 Communications method and apparatus

Publications (1)

Publication Number Publication Date
WO2019196846A1 true WO2019196846A1 (zh) 2019-10-17

Family

ID=67006761

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/081974 WO2019196846A1 (zh) 2018-04-09 2019-04-09 通信方法及装置

Country Status (6)

Country Link
US (2) US11523268B2 (zh)
EP (1) EP3764672A4 (zh)
KR (1) KR102486370B1 (zh)
CN (1) CN109951824B (zh)
BR (1) BR112020020740A2 (zh)
WO (1) WO2019196846A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021136651A1 (en) * 2019-12-31 2021-07-08 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for terminal device availability management
WO2021177793A1 (en) 2020-03-06 2021-09-10 Samsung Electronics Co., Ltd. Apparatus and method for supporting upf event exposure service in wireless communication system
US20230143200A1 (en) * 2020-03-23 2023-05-11 Samsung Electronics Co., Ltd. Upf service-based packet delay status event exposure service method and device

Families Citing this family (36)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200059989A1 (en) * 2017-08-16 2020-02-20 Lenovo (Singapore) Pte. Ltd. Indicating a packet data unit session as unavailable
CN113796108A (zh) * 2019-05-06 2021-12-14 瑞典爱立信有限公司 将用户平面功能映射到用户设备
US11381494B2 (en) 2019-05-07 2022-07-05 Electronics And Telecommunications Research Institute Method and system for providing communication analysis of user equipment based on network data analysis
CN110289928B (zh) * 2019-07-02 2020-07-31 中国联合网络通信集团有限公司 5g网络下应急公共广播方法和系统
CN110267212B (zh) * 2019-07-18 2021-08-03 中国联合网络通信集团有限公司 移动网络建立群组通信的方法及装置
CN112312461B (zh) * 2019-07-29 2024-05-17 中兴通讯股份有限公司 下行数据通知失败检测方法、amf、smf及存储介质
EP3993486A4 (en) * 2019-07-30 2022-08-31 Huawei Technologies Co., Ltd. METHOD, DEVICE AND SYSTEM FOR TRANSMITTING EVENT REPORTS
CN112398891B (zh) * 2019-08-16 2023-04-18 华为技术有限公司 一种通信方法和装置
US20220272175A1 (en) * 2019-08-22 2022-08-25 Lg Electronics Inc. Efficient processing method according to relocation of application server in 5g
CN112437104B (zh) * 2019-08-26 2022-04-15 阿里巴巴集团控股有限公司 服务质量管理的方法及装置、通信系统
CN110430605B (zh) * 2019-09-12 2021-08-24 中国联合网络通信集团有限公司 会话线路切换方法及系统
CN110621032B (zh) * 2019-09-27 2021-06-15 腾讯科技（深圳）有限公司 一种通信的方法、相关装置及设备
CN112584373B (zh) * 2019-09-30 2022-04-22 华为技术有限公司 事件订阅方法和装置
CN112583713B (zh) * 2019-09-30 2023-09-29 中兴通讯股份有限公司 流量路由控制方法、网络设备、系统及存储介质
US20220394580A1 (en) * 2019-10-04 2022-12-08 Ntt Docomo, Inc. Access control apparatus and user plane apparatus
CN113038467B (zh) * 2019-12-06 2022-12-02 华为技术有限公司 一种事件信息上报方法及通信装置
CN113098822B (zh) * 2019-12-20 2022-05-10 华为技术有限公司 一种恢复ims业务的方法及装置
CN113498057A (zh) * 2020-04-03 2021-10-12 华为技术有限公司 通信系统、方法及装置
CN111556539B (zh) * 2020-05-13 2024-05-17 腾讯科技（深圳）有限公司 Ue执行的方法及ue、以及smf实体执行的方法及smf实体
CN111526553A (zh) * 2020-05-13 2020-08-11 腾讯科技（深圳）有限公司 Ue执行的方法及ue、以及smf实体执行的方法及smf实体
US20230353456A1 (en) * 2020-06-28 2023-11-02 Zhiguo Li Network slicing enhancement
CN113938911A (zh) * 2020-07-13 2022-01-14 华为技术有限公司 一种通信方法、设备及系统
CN113973322A (zh) * 2020-07-24 2022-01-25 华为技术有限公司 一种通信方法及装置
CN114071554A (zh) * 2020-07-31 2022-02-18 华为技术有限公司 一种事件通知方法、装置和系统
CN114143185A (zh) * 2020-08-13 2022-03-04 阿里巴巴集团控股有限公司 一种网络通信的方法及装置、电子设备、存储介质
CN112202844B (zh) * 2020-09-10 2022-05-06 中国联合网络通信集团有限公司 一种跨域多接入边缘计算能力开放的方法及设备
CN114390507B (zh) * 2020-10-20 2024-05-03 中国电信股份有限公司 动态触发rfsp值更改的方法和系统
WO2022151399A1 (zh) * 2021-01-15 2022-07-21 华为技术有限公司 事件订阅的方法、装置及系统
WO2022157716A1 (en) * 2021-01-21 2022-07-28 Telefonaktiebolaget Lm Ericsson (Publ) Status event handling associated with a session management function (smf) node
CN112954615B (zh) * 2021-02-10 2023-05-23 腾讯科技（深圳）有限公司 多播广播业务的通信方法、装置、介质及电子设备
CN118042505A (zh) * 2021-07-21 2024-05-14 安科讯(福建)科技有限公司 一种5g通信基于专用qos流的qos流动态调整方法与系统
CN117062080A (zh) * 2021-08-03 2023-11-14 安科讯(福建)科技有限公司 一种基于白名单的QoS流的动态控制方法及终端
CN116094913A (zh) * 2021-11-08 2023-05-09 中国移动通信有限公司研究院 信息传输方法、装置及通信设备
CN115002686B (zh) * 2022-05-23 2023-10-03 中国电信股份有限公司 终端通信方法、装置、计算机存储介质及电子设备
CN117560716A (zh) * 2022-08-04 2024-02-13 华为技术有限公司 通信方法和通信装置
CN115604857B (zh) * 2022-09-27 2023-06-16 广州爱浦路网络技术有限公司 基于信令面进行用户分组监控的方法及系统

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130262576A1 (en) * 2012-04-03 2013-10-03 Telefonaktiebolaget L M Ericsson (Publ) Systems and methods for event notification framework in a machine-to-machine (m2m) context
CN103384380A (zh) * 2012-05-02 2013-11-06 中兴通讯股份有限公司 一种机器类通信事件的上报方法及相应装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2131557B1 (en) 2006-12-29 2014-11-12 Huawei Technologies Co., Ltd. Method and system and network element for service processing after network element data invalidated and occuring fault
US20170366423A1 (en) 2016-06-15 2017-12-21 Qualcomm Incorporated Data packet store, forward, and monitoring functionality for network node or modem
EP3488626B1 (en) 2016-08-22 2022-09-28 Samsung Electronics Co., Ltd. Method and apparatus for providing services of network to terminal by using slice
WO2018121880A1 (en) * 2016-12-30 2018-07-05 Telefonaktiebolaget Lm Ericsson (Publ) Network slice selection
KR20200102474A (ko) * 2018-03-23 2020-08-31 텔레폰악티에볼라겟엘엠에릭슨(펍) Ip 멀티미디어 서브시스템에서의 네트워크 슬라이싱 인식

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130262576A1 (en) * 2012-04-03 2013-10-03 Telefonaktiebolaget L M Ericsson (Publ) Systems and methods for event notification framework in a machine-to-machine (m2m) context
CN103384380A (zh) * 2012-05-02 2013-11-06 中兴通讯股份有限公司 一种机器类通信事件的上报方法及相应装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "Idle Status Indication in MONTE: UE Reachability or Availability after DDN Failure Events", SA WG2 MEETING #120, 31 March 2017 (2017-03-31), pages 2 - 171796, XP051248106 *
See also references of EP3764672A4
ZTE: "Update of Solution 39: UE Availability After DDN Failure for Multiple AFs", SA WG2 MEETING #129, 9 October 2018 (2018-10-09), pages 2 - 1810323, XP051540257 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021136651A1 (en) * 2019-12-31 2021-07-08 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for terminal device availability management
WO2021177793A1 (en) 2020-03-06 2021-09-10 Samsung Electronics Co., Ltd. Apparatus and method for supporting upf event exposure service in wireless communication system
EP4101129A4 (en) * 2020-03-06 2023-03-01 Samsung Electronics Co., Ltd. DEVICE AND METHOD FOR SUPPORTING UPF EVENT EXPOSURE SERVICE IN A WIRELESS COMMUNICATION SYSTEM
US20230143200A1 (en) * 2020-03-23 2023-05-11 Samsung Electronics Co., Ltd. Upf service-based packet delay status event exposure service method and device
US11765055B2 (en) * 2020-03-23 2023-09-19 Samsung Electronics Co., Ltd UPF service-based packet delay status event exposure service method and device
US20240048462A1 (en) * 2020-03-23 2024-02-08 Samsung Electronics Co., Ltd. Upf service-based packet delay status event exposure service method and device

Also Published As

Publication number Publication date
CN109951824A (zh) 2019-06-28
KR20200136985A (ko) 2020-12-08
US20210076192A1 (en) 2021-03-11
EP3764672A1 (en) 2021-01-13
US11523268B2 (en) 2022-12-06
US20230056728A1 (en) 2023-02-23
EP3764672A4 (en) 2021-01-13
CN109951824B (zh) 2022-04-05
KR102486370B1 (ko) 2023-01-06
BR112020020740A2 (pt) 2021-01-19

Similar Documents

Publication Publication Date Title
WO2019196846A1 (zh) 通信方法及装置
WO2020224492A1 (zh) 一种网络数据分析方法及装置
US10812609B2 (en) Service subscription method and system for reporting service change in communications system
RU2728538C1 (ru) Способ для выполнения связанной с регистрацией amf процедуры посредством udm в системе беспроводной связи и устройство для этого
KR20200139771A (ko) 5g 네트워크에서의 로컬 영역 데이터 네트워크(ladn)에 대한 접속들을 관리하는 방법들
US20180109308A1 (en) Mobile device relay service for reliable internet of things
EP3829203A1 (en) Information transmission method and device, and computer readable storage medium
US20210168151A1 (en) Method for implementing user plane security policy, apparatus, and system
WO2023280121A1 (zh) 一种获取边缘服务的方法和装置
WO2019196602A1 (zh) 通信方法、装置及系统
EP3001709B1 (en) Communication terminal and server apparatus
WO2018205114A1 (zh) 一种状态切换方法及装置
WO2019101074A1 (zh) 一种通信方法、装置及系统
KR20200088874A (ko) 베어러 식별자를 결정하기 위한 방법 및 디바이스, 및 그를 위한 저장 매체
EP4192106A1 (en) Communication method and apparatus
EP3883270B1 (en) Method and apparatus for recognizing terminal
WO2019174582A1 (zh) 一种消息传输方法和装置
US20210329504A1 (en) Communication method and apparatus
KR20220158018A (ko) 접속 수립 방법, 통신 장치, 및 시스템
WO2022068771A1 (zh) 一种通信方法及通信装置
RU2786671C2 (ru) Способ связи и устройство
WO2023071634A1 (zh) 一种通信方法及装置
WO2022206296A1 (zh) 一种会话控制的方法、装置和系统
EP3972142B1 (en) Policy control function fallback
WO2022100197A1 (zh) 获取边缘服务的方法和装置

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019785700

Country of ref document: EP

Effective date: 20201006

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112020020740

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 20207031097

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 112020020740

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20201008