CN110557744A - Method for subscribing event and network function network element - Google Patents

Method for subscribing event and network function network element Download PDF

Info

Publication number
CN110557744A
CN110557744A CN201811161672.5A CN201811161672A CN110557744A CN 110557744 A CN110557744 A CN 110557744A CN 201811161672 A CN201811161672 A CN 201811161672A CN 110557744 A CN110557744 A CN 110557744A
Authority
CN
China
Prior art keywords
network element
event
identifier
network
network function
Prior art date
Legal status (The legal status 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 status listed.)
Granted
Application number
CN201811161672.5A
Other languages
Chinese (zh)
Other versions
CN110557744B (en
Inventor
宗在峰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of CN110557744A publication Critical patent/CN110557744A/en
Application granted granted Critical
Publication of CN110557744B publication Critical patent/CN110557744B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • 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/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data

Abstract

The application provides a method for subscribing to an event, which comprises the following steps: a first network function network element sends a first request message to a second network function network element, wherein the first request message is used for requesting a first event subscription to the second network function network element, and the first request message carries an event identifier; a first network function network element receives a first response message sent by a second network function network element, wherein the first response message carries a first identifier, and the first identifier is an identifier distributed for a first event subscription by the second network function network element; a first network function network element receives event report information sent by a third network function network element, wherein the event report information carries an event identifier and a first identifier; the first network function network element determines that the event report information is associated with the first event subscription according to the first identifier. The method can enable the first network function network element to correlate the event subscription of the second network function, which is requested by the first network function network element to the third network function network element, with the event report information sent by the third network function network element.

Description

Method for subscribing event and network function network element
Technical Field
The present application relates to the field of communications, and more particularly, to a method of subscribing to an event and a network functional network element.
Background
Fifth generation (5th-generation, 5G) communication systems support data connectivity and service-enabled deployments. In the 5G system, each network functional network element of the control plane may interact based on services. Among the services provided by the network functional network elements, a common service is an event exposure service, and the main implementation process of the service is as follows: when a consumer (service provider) of a service subscribes to a desired event from a provider (service provider) of the service, the service provider is provided with an address of a reception event, and then the service provider determines that the desired event subscribed by the service subscriber can be provided and notifies the address of the reception event of the desired event.
In an actual event subscription, a consumer of a service may not make an event subscription directly to a provider of the service, but indirectly to the provider of the service. For example, a service consumer subscribes to an event from an intermediate network element, and then the intermediate network element subscribes to the event from a service provider, and finally the service provider notifies the service consumer of the subscribed event.
When a service consumer indirectly subscribes to an event from a service provider, there may be a case where the service consumer cannot associate the received event report information with a previous event subscription, and the service consumer cannot perform other subsequent operations, for example, further report the received event to other network elements.
Disclosure of Invention
The application provides a method for subscribing to an event, which aims to solve the problem of how to associate event report information with a requested event subscription in indirect subscription.
In a first aspect, a method for subscribing to an event is provided, including: a first network function network element sends a first request message to a second network function network element, wherein the first request message is used for requesting a first event subscription to the second network function network element, and the first request message carries an event identifier; the first network function network element receives a first response message sent by the second network function network element, wherein the first response message carries a first identifier, and the first identifier is an identifier which is distributed for the first event subscription by the second network function network element; the first network function network element receives event report information sent by a third network function network element, wherein the event report information carries the event identifier and the first identifier; and the first network function network element determines that the event report information is associated with the first event subscription according to the first identifier.
The correlation identification is generated by having an intermediate network element (e.g., a second network function network element) generate the correlation identification from the event subscription requested by the network element requesting the event subscription (e.g., the first network function network element), and sends the associated identifier (e.g., the first identifier) to the first network function network element and the network element sending the event report (e.g., the third network function network element), and when the third network functional network element receives an event subscription that the second network functional network element requests from the third network functional network element for the first network functional network element, the third network function network element sends the first identifier carried in the event report information to the first network function network element, enabling the first network function network element to determine that the event subscription requested from the second network function network element is associated with the event report information received from the third network function network element according to the association identifier.
As an optional implementation manner, the first reply message and the event report information further carry a second identifier, where the second identifier is used to indicate the second network function network element, and the first identifier and the second identifier are used to be associated with the first event subscription.
In this implementation, the determining, by the first network functional network element according to the first identifier, that the event report information is associated with the first event subscription includes: and the first network function network element determines that the event report information is associated with the first event subscription according to the first identifier and the second identifier.
When the first identifier is not unique, the second network function network element provides an identifier (for example, a second identifier) which uniquely indicates the second network function and the first identifier to the first network function network element and the third network function network element, and when the third network function network element receives an event subscription which is requested by the second network function network element from the first network function network element to the third network function network element, the third network function network element carries the first identifier and the second identifier in event report information and sends the event subscription to the first network function network element, so that the first network function network element can determine that the event subscription which is requested by the second network function network element is associated with the event report information which is received from the third network function network element according to the first identifier and the second identifier.
As an optional implementation manner, the second identifier is an Internet Protocol (IP) address of interconnection between networks of the second network function network element or a Fully Qualified Domain Name (FQDN) of the second network function network element.
In a second aspect, a method for subscribing to an event is provided, including: a second network function network element receives a first request message sent by a first network function network element, wherein the first request message is used for requesting a first event subscription to the second network function network element, and the first request message carries an event identifier; the second network function network element sends a first response message to the first network function network element, wherein the first response message carries a first identifier, and the first identifier is an identifier which is distributed for the first event subscription by the second network function network element; and the second network function network element sends a second request message to a third network function network element, where the second request message is used for requesting a second event subscription from the third network function network element for the first network function network element, and the second request message carries the event identifier and the first identifier.
The correlation identification is generated by having an intermediate network element (e.g., a second network function network element) generate the correlation identification from the event subscription requested by the network element requesting the event subscription (e.g., the first network function network element), and sends the associated identifier (e.g., the first identifier) to the first network function network element and the network element sending the event report (e.g., the third network function network element), and when the third network functional network element receives an event subscription that the second network functional network element requests from the third network functional network element for the first network functional network element, the third network function network element sends the first identifier carried in the event report information to the first network function network element, enabling the first network function network element to determine that the event subscription requested from the second network function network element is associated with the event report information received from the third network function network element according to the association identifier.
As an optional implementation manner, the first reply message and the second request message further carry a second identifier, where the second identifier is used to indicate the second network function network element, and the first identifier and the second identifier are used to be associated with the first event subscription.
When the first identifier is not unique, the second network function network element provides an identifier (for example, a second identifier) which uniquely indicates the second network function and the first identifier to the first network function network element and the third network function network element, and when the third network function network element receives an event subscription which is requested by the second network function network element from the first network function network element to the third network function network element, the third network function network element carries the first identifier and the second identifier in event report information and sends the event subscription to the first network function network element, so that the first network function network element can determine that the event subscription which is requested by the second network function network element is associated with the event report information which is received from the third network function network element according to the first identifier and the second identifier.
As an optional implementation manner, the second identifier is an IP address of the second network function network element or an FQDN of the second network function network element.
In a third aspect, a method for subscribing to an event is provided, including: a third network function network element receives a second request message sent by a second network function network element, wherein the second request message is used for requesting a second event subscription from the third network function network element for a first network function network element, the second request message carries an event identifier and a first identifier, the first identifier is an identifier distributed by the second network function network element for the first event subscription, and the first event subscription is the event subscription requested by the first network function network element to the second network function network element; and the third network function network element sends event report information to the first network function network element according to the second request message, wherein the event report information carries the event identifier and the first identifier.
The correlation identification is generated by having an intermediate network element (e.g., a second network function network element) generate the correlation identification from the event subscription requested by the network element requesting the event subscription (e.g., the first network function network element), and sends the associated identifier (e.g., the first identifier) to the first network function network element and the network element sending the event report (e.g., the third network function network element), and when the third network functional network element receives an event subscription that the second network functional network element requests from the third network functional network element for the first network functional network element, the third network function network element sends the first identifier carried in the event report information to the first network function network element, enabling the first network function network element to determine that the event subscription requested from the second network function network element is associated with the event report information received from the third network function network element according to the association identifier.
As an optional implementation manner, the second request message and the event report information further carry a second identifier, where the second identifier is used to indicate the second network function network element, and the first identifier and the second identifier are used to be associated with the first event subscription.
When the first identifier is not unique, the second network function network element provides an identifier (for example, a second identifier) which uniquely indicates the second network function and the first identifier to the first network function network element and the third network function network element, and when the third network function network element receives an event subscription which is requested by the second network function network element from the first network function network element to the third network function network element, the third network function network element carries the first identifier and the second identifier in event report information and sends the event subscription to the first network function network element, so that the first network function network element can determine that the event subscription which is requested by the second network function network element is associated with the event report information which is received from the third network function network element according to the first identifier and the second identifier.
As an optional implementation manner, the second identifier is an IP address of the second network function network element or an FQDN of the second network function network element.
in a fourth aspect, a method for subscribing to an event is provided, including: a first network function network element sends a first request message to a second network function network element, wherein the first request message is used for requesting a first event subscription to the second network function network element, and the first request message carries an event identifier; the first network function network element receives a first response message sent by the second network function network element, wherein the first response message carries a third identifier, the third identifier is an identifier allocated to a second event subscription by the third network function network element, and the second event subscription is an event subscription requested by the second network function network element to the third network function network element; the first network function network element receives event report information sent by a third network function network element, wherein the event report information carries the event identifier and the third identifier; and the first network function network element determines that the event report information is associated with the first event subscription according to the third identifier.
By enabling the third network function network element to generate the association identifier when receiving the event subscription that the second network function network element requests from the third network function network element for the first network function network element, and sending the association identifier (for example, the third identifier) to the second network function network element, the second network function network element sends the third identifier to the first network function network element, and enables the third network function network element to carry the third identifier in the event report information and send the event report information to the first network function network element, the first network function network element can determine that the event subscription requested from the second network function network element is associated with the event report information received from the third network function network element according to the third identifier.
As an optional implementation manner, the first reply message and the event report information further carry a fourth identifier, where the fourth identifier is used to indicate the third network function network element, and the third identifier and the fourth identifier are used to be associated with the first event subscription.
In this implementation, the determining, by the first network functional network element according to the third identifier, that the event report information is associated with the first event subscription includes: and the first network function network element determines that the event report information is associated with the first event subscription according to the third identifier and the fourth identifier.
When the third identifier is not unique, the third network function network element sends an identifier (for example, a fourth identifier) uniquely indicating the third network function network element and the third identifier to the second network function network element, the second network function network element sends the fourth identifier and the third identifier to the first network function network element, and the third network function network element sends the fourth identifier and the third identifier to the first network function network element in event report information, so that the first network function network element can determine that the event subscription requested to the second network function network element is associated with the event report information received from the third network function network element according to the third identifier and the fourth identifier.
as an optional implementation manner, the fourth identifier is an IP address of the third network function network element or an FQDN of the third network function network element.
In a fifth aspect, a method for event subscription is provided, including: a second network function network element receives a first request message sent by a first network function network element, wherein the first request message is used for requesting a first event subscription to the second network function network element, and the first request message carries an event identifier; the second network function network element sends a second request message to a third network function network element, the second request message carries the event identifier, and the second request message is used for requesting a second event subscription to the third network function network element; the second network function network element receives a second response message sent by a third network function network element, where the second response message carries a third identifier, and the third identifier is an identifier allocated to the second event subscription by the third network function network element; and the second network function network element sends a first response message to the first network function network element, wherein the first response message carries the third identifier.
By enabling the third network function network element to generate the association identifier when receiving the event subscription that the second network function network element requests from the third network function network element for the first network function network element, and sending the association identifier (for example, the third identifier) to the second network function network element, the second network function network element sends the third identifier to the first network function network element, and enables the third network function network element to carry the third identifier in the event report information and send the event report information to the first network function network element, the first network function network element can determine that the event subscription requested from the second network function network element is associated with the event report information received from the third network function network element according to the third identifier.
as an optional implementation manner, the second response message and the first response message further carry a fourth identifier, where the fourth identifier is used to indicate the third network function network element, and the third identifier and the fourth identifier are used to be associated with the first event subscription.
When the third identifier is not unique, the third network function network element sends an identifier (for example, a fourth identifier) uniquely indicating the third network function network element and the third identifier to the second network function network element, the second network function network element sends the fourth identifier and the third identifier to the first network function network element, and the third network function network element sends the fourth identifier and the third identifier to the first network function network element in event report information, so that the first network function network element can determine that the event subscription requested to the second network function network element is associated with the event report information received from the third network function network element according to the third identifier and the fourth identifier.
As an optional implementation manner, the fourth identifier is an IP address of the third network function network element or an FQDN of the third network function network element.
In a sixth aspect, a method for subscribing to an event is provided, including: a third network function network element receives a second request message sent by a second network function network element, wherein the second request message is used for requesting a second event subscription to the third network function network element, and the second request message carries an event identifier; the third network function network element sends a second response message to the second network function network element according to the second request message, wherein the second response message carries a third identifier, and the third identifier is an identifier allocated to the second event subscription by the third network function network element; and the third network function network element sends event report information to the first network function network element, wherein the event report information carries the event identifier and the third identifier.
By enabling the third network function network element to generate the association identifier when receiving the event subscription that the second network function network element requests from the third network function network element for the first network function network element, and sending the association identifier (for example, the third identifier) to the second network function network element, the second network function network element sends the third identifier to the first network function network element, and enables the third network function network element to carry the third identifier in the event report information and send the event report information to the first network function network element, the first network function network element can determine that the event subscription requested from the second network function network element is associated with the event report information received from the third network function network element according to the third identifier.
As an optional implementation manner, the second response message and the event report information further carry a fourth identifier, where the fourth identifier is used to indicate the third network function network element, and the third identifier and the fourth identifier are used to be associated with the first event subscription.
When the third identifier is not unique, the third network function network element sends an identifier (for example, a fourth identifier) uniquely indicating the third network function network element and the third identifier to the second network function network element, the second network function network element sends the fourth identifier and the third identifier to the first network function network element, and the third network function network element sends the fourth identifier and the third identifier to the first network function network element in event report information, so that the first network function network element can determine that the event subscription requested to the second network function network element is associated with the event report information received from the third network function network element according to the third identifier and the fourth identifier.
As an optional implementation manner, the fourth identifier is an IP address of the third network function network element or an FQDN of the third network function network element.
In a seventh aspect, a method for event subscription is provided, including: a first network function network element sends a first request message to a second network function network element, wherein the first request message is used for requesting a first event subscription to the second network function network element and comprises an event identifier; the first network function network element receives a first response message sent by the second network function network element, wherein the first response message includes a fifth identifier, and the fifth identifier is an identifier which is distributed for the first event subscription by the second network function network element; the first network function network element receives an event notification sent by a third network function network element, wherein the event notification comprises the event identifier and the fifth identifier; and the first network function network element determines that the event notification is associated with the first event subscription according to the fifth identifier.
Optionally, the event notification includes event report information. The event notification may specifically be an event notification message. The event notification message includes event report information, and the event report information includes an event identifier and the fifth identifier.
Optionally, the fifth identifier is an identifier of a resource created by the second network function network element for the first event subscription.
By enabling an intermediate network element (for example, a second network function network element) to generate an association identifier according to an event subscription requested by a network element (for example, a first network function network element) requesting an event subscription, and sending the association identifier (for example, a fifth identifier) to the first network function network element and a network element (for example, a third network function network element) sending an event report, and when the third network function network element receives the event subscription requested by the second network function network element from the first network function network element to the third network function network element, enabling the third network function network element to carry the first identifier in an event notification and send the first identifier to the first network function network element, the first network function network element can determine that the event subscription requested by the second network function network element is associated with the event notification received from the third network function network element according to the association identifier
In an eighth aspect, a method for event subscription is provided, including: a second network function network element receives a first request message sent by a first network function network element, wherein the first request message is used for requesting a first event subscription to the second network function network element, and the first request message comprises an event identifier; the second network function network element sends a first reply message to the first network function network element, wherein the first reply message carries a fifth identifier, and the fifth identifier is an identifier which is distributed for the first event subscription by the second network function network element; and the second network function network element sends a second request message to a third network function network element, where the second request message is used for requesting, by the first network function network element, a notification of an event corresponding to the event identifier from the third network function network element, and the second request message includes the event identifier and the fifth identifier.
Optionally, the fifth identifier is an identifier of a resource created by the second network function network element for the first event subscription.
Optionally, the second request message further includes a policy rule, where the policy rule includes the event identifier and the fifth identifier.
By enabling an intermediate network element (for example, a second network function network element) to generate an association identifier according to an event subscription requested by a network element (for example, a first network function network element) requesting an event subscription, and sending the association identifier (for example, a fifth identifier) to the first network function network element and a network element (for example, a third network function network element) sending an event report, and when the third network function network element receives the event subscription requested by the second network function network element from the first network function network element to the third network function network element, enabling the third network function network element to carry the first identifier in an event notification and send the first identifier to the first network function network element, the first network function network element can determine that the event subscription requested by the second network function network element is associated with the event notification received from the third network function network element according to the association identifier
In a ninth aspect, a method for event subscription is provided, including: a third network function network element receives a second request message sent by a second network function network element, wherein the second request message is used for requesting, from the third network function network element, a notification of an event corresponding to an event identifier for a first network function network element, the second request message includes the event identifier and a fifth identifier, the fifth identifier is an identifier allocated by the second network function network element for a first event subscription, and the first event subscription is an event subscription requested by the first network function network element to the second network function network element; and the third network function network element sends an event notification to the first network function network element according to the second request message, wherein the event notification comprises the event identifier and the fifth identifier.
Optionally, the fifth identifier is an identifier of a resource created by the second network function network element for the first event subscription.
Optionally, the second request message further includes a policy rule, where the policy rule includes the event identifier and the fifth identifier.
By enabling an intermediate network element (for example, a second network function network element) to generate an association identifier according to an event subscription requested by a network element (for example, a first network function network element) requesting an event subscription, and sending the association identifier (for example, a fifth identifier) to the first network function network element and a network element (for example, a third network function network element) sending an event report, and when the third network function network element receives the event subscription requested by the second network function network element from the first network function network element to the third network function network element, enabling the third network function network element to carry the first identifier in an event notification and send the first identifier to the first network function network element, the first network function network element can determine that the event subscription requested by the second network function network element is associated with the event notification received from the third network function network element according to the association identifier
In a tenth aspect, a method for event subscription is provided, including: a first network function network element sends a first request message to a second network function network element, wherein the first request message is used for requesting a first event subscription to the second network function network element and comprises an event identifier; the first network function network element receives a first response message sent by the second network function network element, wherein the first response message carries a fifth identifier; the first network function network element acquires a sixth identifier according to the fifth identifier, wherein the sixth identifier is an identifier which is distributed for the first event subscription by the second network function network element; the first network function network element receives an event notification sent by a third network function network element, wherein the event notification comprises the event identifier and the sixth identifier; and the first network function network element determines that the event notification is associated with the first event subscription according to the sixth identifier.
Optionally, the event notification includes event report information. The event notification may specifically be an event notification message. The event notification message includes event report information, and the event report information includes an event identifier and the sixth identifier.
Optionally, the sixth identifier is an identifier of a resource created by the second network function network element for the first event subscription.
by enabling an intermediate network element (e.g., a second network function network element) to generate an intermediate identifier (e.g., a fifth identifier) and an associated identifier (e.g., a sixth identifier) according to an event subscription requested by a network element (e.g., a first network function network element) requesting an event subscription, and sending the intermediate identifier to the first network function network element, and enabling the third network function network element to send an event report to a network element (e.g., a third network function network element) by using the associated identifier, and when the third network function network element receives an event subscription requested by the second network function network element from the third network function network element for the first network function network element, enabling the third network function network element to carry the sixth identifier in an event notification to be sent to the first network function network element, and the first network function network element generates the sixth identifier according to the fifth identifier, enabling the first network function network element to be capable of responding to the sixth identifier, it is determined that the event subscription requested from the second network functional network element is associated with an event notification received from a third network functional network element.
In an eleventh aspect, a method for event subscription is provided, including: a second network function network element receives a first request message sent by a first network function network element, wherein the first request message is used for requesting a first event subscription to the second network function network element, and the first request message comprises an event identifier; the second network function network element sends a first response message to the first network function network element, wherein the first response message carries a fifth identifier; the second network function network element sends a second request message to a third network function network element, where the second request message is used to request, from the third network function network element, a notification of an event corresponding to the event identifier for the first network function network element, and the second request message carries the event identifier and a sixth identifier, where the sixth identifier is an identifier that is distributed by the second network function network element for the first event subscription.
Optionally, the sixth identifier is an identifier of a resource created by the second network function network element for the first event subscription.
Optionally, the second request message further includes a policy rule, where the policy rule includes the event identifier and the sixth identifier.
By enabling an intermediate network element (e.g., a second network function network element) to generate an intermediate identifier (e.g., a fifth identifier) and an associated identifier (e.g., a sixth identifier) according to an event subscription requested by a network element (e.g., a first network function network element) requesting an event subscription, and sending the intermediate identifier to the first network function network element, and enabling the third network function network element to send an event report to a network element (e.g., a third network function network element) by using the associated identifier, and when the third network function network element receives an event subscription requested by the second network function network element from the third network function network element for the first network function network element, enabling the third network function network element to carry the sixth identifier in an event notification to be sent to the first network function network element, and the first network function network element generates the sixth identifier according to the fifth identifier, enabling the first network function network element to be capable of responding to the sixth identifier, it is determined that the event subscription requested from the second network functional network element is associated with an event notification received from a third network functional network element.
in a twelfth aspect, a method for event subscription is provided, including: a third network function network element receives a second request message sent by a second network function network element, wherein the second request message is used for requesting, by the first network function network element, a notification of an event corresponding to an event identifier from the third network function network element, the second request message includes the event identifier and a sixth identifier, the sixth identifier is an identifier allocated by the second network function network element for a first event subscription, and the first event subscription is an event subscription requested by the first network function network element from the second network function network element; and the third network function network element sends an event notification to the first network function network element according to the second request message, wherein the event notification comprises the event identifier and the sixth identifier.
Optionally, the sixth identifier is an identifier of a resource created by the second network function network element for the first event subscription.
Optionally, the second request message further includes a policy rule, where the policy rule includes the event identifier and the sixth identifier.
By enabling an intermediate network element (e.g., a second network function network element) to generate an intermediate identifier (e.g., a fifth identifier) and an associated identifier (e.g., a sixth identifier) according to an event subscription requested by a network element (e.g., a first network function network element) requesting an event subscription, and sending the intermediate identifier to the first network function network element, and enabling the third network function network element to send an event report to a network element (e.g., a third network function network element) by using the associated identifier, and when the third network function network element receives an event subscription requested by the second network function network element from the third network function network element for the first network function network element, enabling the third network function network element to carry the sixth identifier in an event notification to be sent to the first network function network element, and the first network function network element generates the sixth identifier according to the fifth identifier, enabling the first network function network element to be capable of responding to the sixth identifier, it is determined that the event subscription requested from the second network functional network element is associated with an event notification received from a third network functional network element.
In a thirteenth aspect, there is provided a first network function network element, configured to perform the method for subscribing to an event in the first aspect or any possible implementation manner of the first aspect.
In particular, the first network function network element may comprise means for performing the method of the first aspect or any possible implementation of the first aspect for subscribing to events.
As an optional implementation manner, the first network function network element is configured to execute a method for subscribing to an event in any possible implementation manner of the fourth aspect or the fourth aspect.
In particular, the first network function network element may comprise means for performing the method of subscribing to events in the fourth aspect or any possible implementation manner of the fourth aspect.
As another optional implementation manner, the first network function network element is configured to perform a method for subscribing to an event in any possible implementation manner of the seventh aspect or the seventh aspect.
In particular, the first network function network element may comprise means for performing the method of subscribing to events in the seventh aspect or any possible implementation manner of the seventh aspect.
As another optional implementation manner, the first network function network element is configured to perform a method for subscribing to an event in any possible implementation manner of the tenth aspect or the tenth aspect.
In particular, the first network functional network element may comprise means for performing the method of subscribing to events in any possible implementation form of the tenth aspect or the tenth aspect.
In a fourteenth aspect, a first network functional network element is provided that includes a processor and a transceiver. Wherein the processor and the transceiver communicate with each other through an internal connection path.
Optionally, the first network functional network element further comprises a memory for storing instructions, and the processor is configured to execute the instructions stored by the memory.
as an alternative implementation, the processor performs the method of the first aspect or any possible implementation of the first aspect.
As another alternative implementation, the processor performs the method of the fourth aspect or any possible implementation of the fourth aspect.
as another alternative implementation, the processor performs the method of the seventh aspect or any possible implementation of the seventh aspect.
As another alternative implementation, the processor performs the method of the tenth aspect or any possible implementation of the tenth aspect.
in a fifteenth aspect, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method of the first aspect or any of its possible implementations.
As an alternative implementation, the program when executed by a processor implements the method of the fourth aspect or a possible implementation of any of the fourth aspects.
As an alternative implementation, the program when executed by a processor implements the method of any of the seventh aspect or possible implementations of the seventh aspect.
As an alternative implementation, the program when executed by a processor implements the method of the tenth aspect or a possible implementation of any of the tenth aspects.
In a sixteenth aspect, there is provided a computer program product comprising: computer program code which, when executed by a communication unit, a processing unit or a transceiver, a processor of a first network functional network element, causes the first network functional network element to perform the method of the first aspect as described above.
As an alternative implementation, the computer program code, when executed by a communication unit, a processing unit or a transceiver, a processor of the first network functional network element, causes the first network functional network element to perform the method of the fourth aspect described above.
As another alternative implementation, the computer program code, when executed by a communication unit, a processing unit or a transceiver, a processor of the first network functional network element, causes the first network functional network element to perform the method of the seventh aspect described above.
As another alternative implementation, the computer program code, when executed by a communication unit, a processing unit or a transceiver, a processor of the first network functional network element, causes the first network functional network element to perform the method of the tenth aspect described above.
In a seventeenth aspect, a chip system is provided, comprising: a processor configured to support a first network function network element to implement the method of the first aspect.
as an optional implementation manner, the processor in the chip system is configured to support the first network function network element to implement the method of the fourth aspect.
As another optional implementation manner, a processor in the chip system is configured to support the first network function network element to implement the method of the seventh aspect.
as another optional implementation manner, the processor in the chip system is configured to support the first network function network element to implement the method of the tenth aspect.
In an eighteenth aspect, there is provided a second network function network element, configured to perform the method for subscribing to an event in the second aspect or any possible implementation manner of the second aspect.
in particular, the second network function network element may comprise means for performing the method of subscribing to events in the second aspect or any possible implementation of the second aspect.
As an optional implementation manner, the second network function network element is configured to execute a method for subscribing to an event in any possible implementation manner of the fifth aspect or the fifth aspect.
In particular, the second network function network element may comprise means for performing the method of subscribing to events in the fifth aspect or any possible implementation form of the fifth aspect.
As another optional implementation manner, the second network function network element is configured to perform a method for subscribing to an event in the above-mentioned eighth aspect or any possible implementation manner of the eighth aspect.
in particular, the second network function network element may comprise means for performing the method of subscribing to events in the eighth aspect or any possible implementation manner of the eighth aspect.
As another optional implementation manner, the second network function network element is configured to perform a method for subscribing to an event in any possible implementation manner of the eleventh aspect or the eleventh aspect.
In particular, the second network functional network element may comprise means for performing the method of subscribing to events in the eleventh aspect or any possible implementation form of the eleventh aspect.
In a nineteenth aspect, a second network function network element is provided that includes a processor and a transceiver. Wherein the processor and the transceiver communicate with each other through an internal connection path.
Optionally, the second network function network element further comprises a memory for storing instructions, and the processor is configured to execute the instructions stored by the memory.
As an alternative implementation, the processor performs the second aspect or the method of any possible implementation of the second aspect.
As another alternative implementation, the processor performs the method of the fifth aspect or any possible implementation of the fifth aspect.
As another alternative implementation, the processor performs the method of the eighth aspect or any possible implementation of the eighth aspect.
As another alternative implementation, the processor performs the method of the eleventh aspect or any possible implementation of the eleventh aspect.
A twentieth aspect provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method of the second aspect or a possible implementation of any of the second aspects.
As an alternative implementation, the program when executed by a processor implements the method of the fifth aspect or a possible implementation of any of the fifth aspects.
As an alternative implementation, the program when executed by a processor implements the method of the eighth aspect or a possible implementation of any of the eighth aspects.
As an alternative implementation, the program when executed by a processor implements the method of any of the eleventh aspects or possible implementations of the eleventh aspect.
In a twenty-first aspect, there is provided a computer program product comprising: computer program code which, when executed by a communication unit, processing unit or transceiver, processor of a second network functional network element, causes the second network functional network element to perform the method of the second aspect as described above.
As an alternative implementation, the computer program code, when executed by a communication unit, a processing unit or a transceiver, a processor of the second network functional network element, causes the second network functional network element to perform the method of the above-mentioned fifth aspect.
As another alternative implementation, the computer program code, when executed by a communication unit, a processing unit or a transceiver, a processor of the second network functional network element, causes the second network functional network element to perform the method of the above-mentioned eighth aspect.
as another alternative implementation, the computer program code, when executed by a communication unit, a processing unit or a transceiver, a processor of the second network functional network element, causes the second network functional network element to perform the method of the eleventh aspect described above.
In a twenty-second aspect, there is provided a chip system comprising: a processor configured to support a second network function network element to implement the method of the second aspect.
As an optional implementation manner, the processor in the chip system is configured to support the second network function network element to implement the method of the fifth aspect.
as another optional implementation manner, a processor in the chip system is configured to support a second network function network element to implement the method of the above-mentioned eighth aspect.
As another optional implementation manner, the processor in the chip system is configured to support the second network function network element to implement the method of the eleventh aspect.
A twenty-third aspect provides a third network function network element, configured to perform the method for subscribing to an event in the third aspect or any possible implementation manner of the third aspect.
In particular, the third network function network element may comprise means for performing the method of subscribing to events in the third aspect or any possible implementation manner of the third aspect.
as an optional implementation manner, the third network function network element is configured to execute a method for subscribing to an event in the sixth aspect or any possible implementation manner of the sixth aspect.
In particular, the third network functional network element may comprise means for performing the method of subscribing to events in any possible implementation form of the sixth aspect or the sixth aspect.
As another optional implementation manner, the third network function network element is configured to perform a method for subscribing to an event in any possible implementation manner of the ninth aspect or the ninth aspect.
In particular, the third network functional network element may comprise means for performing the method of subscribing to events in any possible implementation form of the ninth aspect or the ninth aspect.
As another optional implementation manner, the third network function network element is configured to perform a method for subscribing to an event in any possible implementation manner of the twelfth aspect or the twelfth aspect.
In particular, the third network functional network element may comprise means for performing the method of subscribing to events in the twelfth aspect or any possible implementation form of the twelfth aspect.
in a twenty-fourth aspect, a third network functional network element is provided that includes a processor and a transceiver. Wherein the processor and the transceiver communicate with each other through an internal connection path.
Optionally, the third network functional network element further comprises a memory for storing instructions, and the processor is configured to execute the instructions stored by the memory.
As an alternative implementation, the processor performs the third aspect or the method in any possible implementation of the third aspect.
As another alternative implementation, the processor performs the method of the sixth aspect or any possible implementation of the sixth aspect.
As another alternative implementation, the processor performs the method of the ninth aspect or any possible implementation of the ninth aspect.
As another alternative implementation, the processor performs the method of the twelfth aspect or any possible implementation of the twelfth aspect.
A twenty-fifth aspect provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method of the third aspect or any of its possible implementations.
As an alternative implementation, the program when executed by a processor implements the method of the sixth aspect or a possible implementation of any of the sixth aspects.
As an alternative implementation, the program when executed by a processor implements the method of any of the ninth aspect or possible implementations of the ninth aspect.
As an alternative implementation, the program when executed by a processor implements the method of the twelfth aspect or a possible implementation of any of the twelfth aspects.
In a twenty-sixth aspect, there is provided a computer program product comprising: computer program code which, when run by a communication unit, a processing unit or a transceiver, a processor of a third network functional network element, causes the third network functional network element to perform the method of the above-mentioned third aspect.
As an alternative implementation, the computer program code, when executed by a communication unit, a processing unit or a transceiver, a processor of the third network functional network element, causes the third network functional network element to perform the method of the above-mentioned sixth aspect.
As another alternative implementation, the computer program code, when executed by a communication unit, a processing unit or a transceiver, a processor of the third network functional network element, causes the third network functional network element to perform the method of the ninth aspect described above.
As another alternative implementation, the computer program code, when executed by a communication unit, a processing unit or a transceiver, a processor of the third network functional network element, causes the third network functional network element to perform the method of the twelfth aspect described above.
In a twenty-seventh aspect, there is provided a chip system comprising: a processor configured to support a third network function network element to implement the method of the third aspect.
As an optional implementation manner, the processor in the chip system is configured to support a third network function network element to implement the method of the sixth aspect.
As another optional implementation manner, the processor in the chip system is configured to support a third network function network element to implement the method of the ninth aspect.
As another optional implementation manner, the processor in the chip system is configured to support a third network function network element to implement the method of the twelfth aspect.
A twenty-eighth aspect provides a communication system comprising one or more of the aforementioned first network functional network element, second network functional network element and third network functional network element.
In a possible design, the communication system may further include other devices that interact with the first network function network element, the second network function network element, or the third network function network element in the solution provided in this embodiment, and so on.
drawings
Fig. 1 is a network architecture applied to an embodiment of the present application.
Fig. 2 is a schematic interaction diagram of a general method 200 of subscribing to an event.
Fig. 3 is another schematic interaction diagram of a general method 300 of subscribing to an event.
Fig. 4 is a schematic interaction diagram of a method 400 for subscribing to an event according to an embodiment of the present application.
Fig. 5 is a schematic interaction diagram of a method 500 for subscribing to an event according to an embodiment of the present application.
Fig. 6 is a schematic interaction diagram of a method 600 for subscribing to an event according to an embodiment of the present application.
Fig. 7 is a schematic interaction diagram of a method 700 for subscribing to an event according to an embodiment of the present application.
Fig. 8 is a schematic interaction diagram of a method 800 for subscribing to an event according to an embodiment of the present application.
fig. 9 is a schematic interaction diagram of a method 900 for subscribing to an event according to an embodiment of the present application.
Fig. 10 is a schematic interaction diagram of a method 600 for subscribing to an event according to an embodiment of the present application.
Fig. 11 is a schematic interaction diagram of a method 700 for subscribing to an event according to an embodiment of the present application.
Fig. 12 is a schematic interaction diagram of a method 800 for subscribing to an event according to an embodiment of the present application.
Fig. 13 is a schematic interaction diagram of a method 900 for subscribing to an event according to an embodiment of the present application.
Fig. 14 is a schematic block diagram of a first network function network element according to an embodiment of the present application.
fig. 15 is a schematic block diagram of a second network function network element according to an embodiment of the present application.
Fig. 16 is a schematic block diagram of a third network function network element according to an embodiment of the present application.
Fig. 17 is another schematic block diagram of a first network function network element according to an embodiment of the present application.
Fig. 18 is another schematic block diagram of a second network function network element according to an embodiment of the present application.
Fig. 19 is another schematic block diagram of a third network function network element according to an embodiment of the present application.
Detailed Description
The technical solution in the present application will be described below with reference to the accompanying drawings.
Fig. 1 is a network architecture applied to an embodiment of the present application. As shown in fig. 1, the network architecture is described from the perspective of a service interface, and each network element involved in the network architecture is separately illustrated.
1. (radio access network, (R) AN) network element: the method is used for providing a network access function for authorized users in a specific area, and can use transmission tunnels with different qualities according to the level of the users, the requirements of services and the like. (R) the AN network element can manage wireless resources and provide access service for the terminal equipment so as to complete the forwarding of control signals and user data between the terminal equipment and the core network, and can also be understood as a base station in a traditional network;
2. A user plane network element: for packet routing and forwarding, quality of service (QoS) handling of user plane data, etc.
In the 5G communication system, the user plane network element may be a User Plane Function (UPF) network element. In a future communication system, the user plane network element may still be a UPF network element, or may also have another name, which is not limited in this application.
3. A data network element: a network for providing data transmission, in a 5G communication system, the data network element may be a Data Network (DN) element. In future communication systems, the data network element may still be a DN element, or may also have another name, which is not limited in this application.
4. Accessing a management network element: the method is mainly used for mobility management, access management and the like, and can be used for realizing other functions except session management in Mobility Management Entity (MME) functions, such as functions of lawful interception, access authorization/authentication and the like.
In the 5G communication system, the access management network element may be an access and mobility management function (AMF) network element. In a future communication system, the access management network element may still be an AMF network element, or may also have another name, which is not limited in this application.
5. A session management network element: the method is mainly used for session management, Internet Protocol (IP) address allocation and management of terminal equipment, selection of a termination point capable of managing a user plane function, a policy control and charging function interface, downlink data notification and the like.
In the 5G communication system, the session management network element may be a Session Management Function (SMF) network element. In future communication systems, the session management network element may still be an SMF network element, or may also have another name, which is not limited in this application.
6. Network open network element: for securely opening services and capabilities etc. provided by the 3GPP network function element to the outside.
In the 5G communication system, the network open network element may be a network open function (NEF) network element. In future communication systems, the network open network element may still be an NEF network element, or may also have another name, which is not limited in this application.
7. The strategy control network element: the unified policy framework is used for guiding network behavior, providing policy rule information for control plane function network elements (such as AMF, SMF network elements and the like), and the like.
In a 5G communication system, the policy control network element may be a Policy Control Function (PCF) network element. In future communication systems, the policy control network element may still be a PCF network element, or may also have another name, which is not limited in this application.
8. unified data management network element: for handling subscriber identities, access authentication, registration, mobility management, etc.
In the 5G communication system, the unified data management network element may be a Unified Data Management (UDM) network element. In future communication systems, the unified data management may still be a UDM network element, or may also have other names, which is not limited in this application.
9. The application network element: the method is used for carrying out data routing of application influence, accessing to a network open function network element, carrying out strategy control by interacting with a strategy framework and the like.
in the 5G communication system, the application network element may be an Application Function (AF) network element. In a future communication system, the application network element may still be an AF network element, or may also have another name, which is not limited in this application.
10. The terminal equipment: may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem with wireless communication capabilities, as well as various forms of terminals, Mobile Stations (MSs), terminals (terminals), User Equipment (UEs), soft terminals, etc., such as water meters, electricity meters, sensors, etc.
it is to be understood that the above network elements or functions may be network elements in a hardware device, or may be software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform).
In the network architecture, Namf is a service-based interface exhibited by the AMF network element 150, Nsmf is a service-based interface exhibited by the SMF160 network element, Nnef is a service-based interface exhibited by the NEF network element 170, Npcf is a service-based interface exhibited by the PCF network element 180, Nudm is a service-based interface exhibited by the UDM network element 190, and Naf is a service-based interface exhibited by the AF network element 1110. N1 is a reference point between UE110 and AMF network element 150, N2 is a reference point of (R) AN network element 120 and AMF network element 150, which is used for sending non-access stratum (NAS) messages, etc.; n3 is a reference point between (R) AN network element 120 and UPF network element 130, for transmitting user plane data, etc.; n4 is a reference point between the SMF network element 160 and the UPF network element 130, and is used to transmit information such as tunnel identification information, data cache indication information, and downlink data notification message of the N3 connection; the N6 interface is a reference point between the UPF network element 130 and the DN network element 140 for transmitting user plane data and the like.
It should be understood that the network architecture applied to the embodiment of the present application is only an exemplary network architecture described in the service architecture, and the network architecture to which the embodiment of the present application is applied is not limited thereto, and any network architecture capable of implementing the functions of the network elements described above is applicable to the embodiment of the present application.
For example, in some network architectures, network functional network element entities such as the AMF network element 150, the SMF network element 160, the PCF network element 180, the UDM network element 190, and the like are all called network functional network element (NF) network elements; alternatively, in other network architectures, the set of network elements such as AMF network element 160, SMF network element 170, PCF network element 1110, UDM network element 1120, and the like may all be referred to as control plane function network elements.
Among the various services provided by the respective network elements described above, there is one called Event Exposure service (Event Exposure), which provides the following three operations:
Subscription (subscribe): by this operation, a consumer of the service (service provider) subscribes to events of interest to the consumer of the service to a provider of the service (service provider).
Unsubscribe (unsubscribe): the service provider cancels the previous subscription to the service provider by this operation.
Notification (notify): the service provider notifies the service provider of the satisfaction of the previously subscribed event through this operation.
The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a global system for mobile communications (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) system, a General Packet Radio Service (GPRS), a long term evolution (long term evolution, LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication system, a future fifth (5 generation, 5G) system, a new radio Network (NR), or the like.
Terminal equipment in the embodiments of the present application may refer to user equipment, access terminals, subscriber units, subscriber stations, mobile stations, remote terminals, mobile devices, user terminals, wireless communication devices, user agents, or user devices. The terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a future 5G network or a terminal device in a future evolved Public Land Mobile Network (PLMN), and the like, which are not limited in this embodiment.
The network device in this embodiment may be a device for communicating with a terminal device, where the network device may be a Base Transceiver Station (BTS) in a global system for mobile communications (GSM) system or a Code Division Multiple Access (CDMA) system, may also be a base station (nodeB, NB) in a Wideband Code Division Multiple Access (WCDMA) system, may also be an evolved node b (eNB or eNodeB) in an LTE system, may also be a wireless controller in a Cloud Radio Access Network (CRAN) scenario, or may be a relay station, an access point, a vehicle-mounted device, a wearable device, a network device in a future 5G network, or a network device in a future evolved PLMN network, and the like, and the present embodiment is not limited.
In the present application, the event subscription requested by the service consumer to the service provider may be requesting location information of the UE, or may be requesting reachability of the UE or roaming state of the UE.
A general method 200 for subscribing to an event in the prior art will be described below with reference to fig. 2, taking as an example any two NF network elements described above as a consumer and a provider of a service (hereinafter, an NF network element as a consumer of a service is referred to as a first NF network element, and an NF network element as a provider of a service is referred to as a second NF network element). The method 200 includes the following steps.
The first NF network element receives a trigger, which may be from another NF network element (e.g., an AF network element) or internal, and decides to subscribe an event to the second NF network element, where the trigger from the AF may be that the AF network element subscribes an event to the NEF network element.
202, a first NF network element sends an Event open service subscription Request (Nnf _ EventExposure _ Subscribe Request) message to a second NF network element, where Nnf is a service-based interface presented by the first NF network element, and the Nnf _ EventExposure _ Subscribe Request message carries an Event identifier Event Id to be subscribed.
In addition, the request message also carries an identifier of a UE to which the Event subscription is directed, a group identifier, or an indication of any UE, and the Event Id may be a list of one or more events.
Specifically, a first NF network element sends a hyperText transfer protocol (HTTP) POST message to a second NF network element, and a message body of the HTTP POST message carries an Event Id and a Uniform Resource Locator (URL) of a received Event report (Event notification) Event notification URL.
In addition, the HTTP POST message also carries the URL of the request. For example, the URL of the request is: { apiRoot }/nnf-event-exposure/v 1/subscriptions/.
And 203, the second NF network element stores subscription information and distributes a correlation identifier (Co-relation ID) for the event subscription from the first NF network element, wherein the Co-relation ID is used for enabling the first NF network element to correlate the event report and the event subscription when the event report is carried out in the future.
Specifically, the second NF network element creates a resource for the event subscription according to the information carried in the message body of the HTTP POST message, generates a sub-resource identifier (substentid), and constructs a Uniform Resource Identifier (URI) for the created resource. The URI is generated using the URL of the request as a parent resource (parentresource) rejoining the child resource identification.
For example, the URI is { apiRoot }/nnf-event-issue/v 1/subscriptions, and the Co-relationship ID allocated by the second NF network element for the event subscription requested by the first NF network element may be the aforementioned subscriptions ID.
204, the second NF network element returns an event open service Response (Nnf _ EventExposure _ Subscribe Response) message to the first NF network element, wherein the Nnf _ EventExposure _ Subscribe Response message carries the Co-relation ID.
Specifically, the second NF network element sends an HTTP Response (Response) message to the first NF network element, where the HTTP Response message includes a Status Code (Status Code)201Created, a header field (header), and a message body. Wherein, the URI generated in step 203 is carried in the header field, and the status code "201 Created" indicates that the event subscription requested by the first NF network element from the second NF network element is successful.
Optionally, the Co-relation ID carried in the message body of the HTTP Response message is a subscription ID.
The second NF network element detects an Event that can be monitored by the second NF network element and matches the Event Id 205.
206, the second NF network element sends an event open service notification Request (Nnf _ EventExposure _ Notify Request) message to the first NF network element, where the Nnf _ EventExposure _ Notify Request message carries event report information for an event subscription of the first NF network element.
Specifically, the second NF network element sends an HTTP POST message to the first NF network element, and a message body of the Event open service notification request message carries the detected Event Id and subscriptionid.
207, the first NF network element returns an event open service notification response (Nnf _ EventExposure _ Notify reply) message to the second NF network element.
Specifically, the first NF network element and the second NF network element send HTTP Response messages, where the HTTP Response messages carry Status codes (Status codes) 200OK, and the "200 OK" indicates that event report information returned by the second NF network element is successfully received.
And 208, after a period of time, the first NF network element decides to Unsubscribe, and the first NF network element sends an event open service Unsubscribe Request (Nnf _ EventExposure _ ubscrimber Request) message to the second NF network element.
Specifically, the first NF network element sends an HTTP Delete to the second NF network element, and the URL of the request is: { apiRoot }/nnf-event-issue/v 1/subscriptions id.
209, the second NF network element deletes the event subscription requested by the first NF network element.
Specifically, the second NF network element deletes the resource corresponding to the request URL.
210, the second NF network element sends an event open service unsubscribe response to the first NF network element
(Nnf _ EventExposure _ Unscubscripte Response) message.
Specifically, the second NF network element sends an HTTP Response message to the first NF network element, where the HTTP Response message carries a Status Code (Status Code)200OK, and the Status Code "200 OK" indicates that the unsubscribe is successful.
As can be seen from fig. 2, in the prior art, a first NF network element obtains a Co-relation ID returned by a second NF network element when performing an event subscription, and when receiving event report information returned by the second NF network element, the first NF network element associates the event report information with the event subscription according to the Co-relation ID carried by the event report information and the Co-relation ID obtained when performing the event subscription.
In the prior art, there is another case: the network element requesting the event subscription requests another network element for the event subscription through the intermediate network element, for example, the first NF network element requests the second NF network element for the event subscription, and the second NF network element judges that it cannot detect the event corresponding to the event subscription, at this time, the second NF network element requests the third NF network element for the event subscription, and the third NF network element sends the event report information corresponding to the event subscription to the first NF network element.
It can be seen that the network element requesting an event subscription (the first NF network element) requests an event subscription from another network element (the third NF network element) through the intermediate network element (the second NF network element).
In the following, taking the first NF network element as the NEF network element 170, the second NF network element as the UDM network element 190, and the third NF network element as the AMF network element 150 as an example, the method 300 for subscribing to an event is described with reference to fig. 3, for a case that a network element requesting an event subscription requests another network element for an event subscription through an intermediate network element. The method 300 includes the following steps.
301, the NEF network element receives the trigger and decides to subscribe to the UDM network element for the event. The trigger may be from other NF network elements (e.g., AF network elements) or internal, where the trigger from the AF may be an event subscription from the AF network element to the NEF network element.
302, the NEF network element sends an event open service subscription Request (numdm _ EventExposure _ Subscribe Request) message to the UDM network element, where the numdm is a service-based interface presented by the UDM network element, and the numdm _ EventExposure _ Subscribe Request message carries an event identifier EventId1 of an event to be subscribed. EventId1 may be a list of one or more events.
In addition, the Nudm _ EventExposure _ Subscribe Request message also carries an identifier of the UE to which the event subscription is directed, a group identifier of the UE, or an indication of any UE.
Specifically, the NEF network element sends an HTTP POST message to the UDM network element, and a message body of the HTTP POST message carries an Event Id1 and a uniform resource locator neffevent Notification URL of the received Event report.
In addition, the HTTP POST message also carries the requested URL 1. For example, the URL1 for the request is: { apiRoot }/numm-event-exposure/v 1/subscriptions/.
303, the UDM network element stores the subscription information and allocates an association ID1 for the event subscription from the NEF network element, where the Co-association ID1 is used to enable the UDM network element to associate the event report with the event subscription when the event report is performed in the future.
Specifically, the UDM network element creates a resource for the event subscription according to the information carried in the message body of the HTTP POST message, generates a child resource identifier subscriptionid1, and constructs a URI1 for the created resource, where the URI1 is generated by concatenating the child resource identifier with the URL1 of the request as a parent resource (parent resource).
For example, the URI1 is { apiRoot }/numm-event-issue/v 1/subscriptions ID1, and the Co-relationship ID1 allocated by the UDM network element for the event subscription requested by the NEF network element may be the aforementioned subscriptions ID 1.
304, if the UDM network element determines that the Event carried in the Event identifier Evnet Id1 cannot be detected, the UDM network element sends an Event open service subscription Request (Namf _ EventExposure _ Subscribe Request) message to the AMF network element, where Namf is a service-based interface displayed by the AMF network element, the Namf _ EventExposure _ Subscribe Request message carries an Event identifier Event Id1 to be subscribed, and the Event Id1 may be a list of one or more events. This message may be considered that UDM subscribes to the AMF for NEF for Event report corresponding to Event Id 1.
In addition, the second request message also carries an identifier of the UE to which the event subscription is directed, a group identifier of the UE, or an indication of any UE.
Specifically, the UDM network element sends an HTTP POST message to the AMF network element, and a message body of the HTTP POST message carries an Event Id1 and a uniform resource locator neffevent Notification URL of receiving an Event report.
In addition, the HTTP POST message also carries a URL2 of the request, for example, the URL2 of the request is: { apiRoot }/namf-event-exposure/v 1/subscriptions/.
305, the AMF network element stores subscription information, and allocates an association identifier Co-relation ID2 for the event subscription from the UDM network element, wherein the Co-relation ID2 is used for enabling the UDM network element to associate the event report with the event subscription when the event report is carried out in the future.
Specifically, the AMF network element creates a resource for the event subscription according to the information carried in the message body of the HTTP POST message, generates a child resource identifier subscriptionid2, and constructs a URI2 for the created resource, where the URI2 is generated by splicing a requested URL2 as a parent resource (parent resource) with the child resource identifier.
For example, the URI2 is { apiRoot }/namf-event-issue/v 1/descriptions 2, and the Co-relation ID2 allocated by the AMF network element to the UDM network element may be the above-mentioned descriptions ID 2.
306, the AMF network element returns an event open service Response (Namf _ EventExposure _ Subscribe Response) message to the UDM network element, the Namf _ EventExposure _ Subscribe Response message carrying the Co-relationship id 2.
specifically, the AMF network element returns an HTTP Response message to the UDM network element, where the HTTP Response message includes a Status Code (Status Code)201Created, a header field (header), and a message body. Wherein, the URI2 generated in step 305 is carried in the header field, and the status code "201 Created" indicates that the event subscription of the UDM network element is successful.
Optionally, the Co-relation ID2 carried in the message body of the HTTP Response message is a subscription ID 2.
307, the UDM network element returns an event open service Response (numdm _ EventExposure _ Subscribe Response) message to the NEF network element, where the numdm _ EventExposure _ Subscribe Response message carries Co-relation ID 1.
Specifically, the UDM network element returns an HTTP Response message to the NEF network element, where the HTTP Response message includes a Status Code (Status Code)201Created, a header field (header), and a message body. The URI1 generated in step 303 is carried in the header field, and the status code "201 Created" indicates that the event subscription of the NEF element is successful.
Optionally, the Co-relation ID1 carried in the message body of the HTTP Response message is a subscription ID 1.
308, the AMF network element detects an Event that can be monitored by the AMF network element and matches the Event Id 1.
309, the AMF network element sends an event open service notification Request (Namf _ EventExposure _ Notify Request) message to the NEF network element, where the Namf _ EventExposure _ Notify Request message carries an event report for an event subscription of the UDM network element.
Specifically, the AMF network element sends an HTTP POST message to the NEF network element, and the message body of the Event openservice notification request message carries the Event Id1 and the subscriptionid2 detected by the AMF network element. Wherein, Namf is a service-based interface exposed by the AMF.
At 310, the NEF network element returns an event open service notification Response (Namf _ EventExposure _ Notify Response) message to the AMF network element.
Specifically, the NEF network element sends an HTTP Response message to the AMF network element, where the HTTP Response message carries a Status Code (Status Code)200OK, and the "200 OK" indicates that the event report returned by the AMF network element is successfully received.
As can be seen from the method 300, the NEF network element requests an event subscription to the UDM network element, and the UDM network element allocates an association identifier 1 to the event subscription according to the event subscription requested by the NEF network element. And if the UDM network element judges that the UDM network element cannot detect the event corresponding to the event subscription, the UDM network element requests the AMF network element for the event subscription, the AMF network element distributes an associated identifier 2 for the event subscription requested by the NEF network element according to the UDM network element, and the associated identifier 2 is carried in event report information and is sent to the NEF network element.
However, the NEF network element cannot associate the event report information with the event subscription requested by the NEF network element from the UDM network element according to the association identifier 2 carried in the event report sent by the AMF network element, and therefore, corresponding operations cannot be performed, for example, further reporting the detected event to other network elements.
therefore, the present application provides a method for subscribing to an event, in response to a situation that a network element requesting an event subscription requests an event subscription to another network element through an intermediate network element, by enabling the intermediate network element to generate an association identifier according to the event subscription requested by the network element requesting the event subscription, and sending the association identifier to the network element requesting the event subscription and another network element, and when the other network element receives the event subscription requested by the network element requesting the event subscription to the other network element for the intermediate network element requesting the event subscription, enabling the other network element to carry the association identifier in event report information and send the association identifier to the network element requesting the event subscription, so that the network element requesting the event subscription can determine, according to the association identifier, that the event subscription requested to the intermediate network element is associated with the event report information received from the other network element.
Next, a method for subscribing to an event according to an embodiment of the present application is described with reference to fig. 4 to 9.
Fig. 4 is a schematic flow chart of a method 400 for subscribing to an event according to an embodiment of the present application.
It should be noted that, the first network functional network element described below may be the NEF network element 170 in fig. 1, the second network functional network element may be the UDM network element 190 in fig. 1, and the third network functional network element may be the AMF network element 150 in fig. 1; alternatively, the first network functional network element may be the NEF network element 170 in fig. 1, the second network functional network element may be the PCF network element 180 in fig. 1, and the third network functional network element may be the SMF network element 160 in fig. 1, which will not be described in detail later. The method 400 includes at least the following steps.
401, a first network function network element sends a first request message to a second network function network element, where the first request message is used to request a first event subscription from the second network function network element, and the first request message carries an event identifier.
Specifically, by way of example and not limitation, a first network function network element sends an Event open service subscription Request (Nnf2_ eventeExposure _ SubscribeRequest) message (e.g., a first Request message) to a second network function network element, Nnf2 is a service-based interface exposed by the second network function network element, the first Request message carries an Event Id1 (e.g., an Event identifier), and further carries any one of an identifier of a UE for which the first Event subscription is intended, a group identifier of the UE, and indication information indicating that the first Event subscription is intended for any UE, and a uniform resource locator Nf1Event Notification of a reception Event report, the first Request message is used for requesting an Event subscription (e.g., a first Event subscription) from a URL to the second network function network element.
In addition, the first request message also carries the requested URL 1. For example, the URL1 of the request is that the URL is: { apiRoot }/nnf2-event-exposure/v 1/subscriptions/.
402, a second network function network element receives a first request message sent by a first network function network element, where the first request message is used to request a first event subscription from the second network function network element, and the first request message carries an event identifier.
Specifically, by way of example and not limitation, the second network function network element receives the first request message sent by the first network function network element, creates a resource for the first event subscription according to the information in the first request message, generates a child resource identifier 1 (e.g., a subscriptionid1), and constructs a uniform resource locator identifier 1 (e.g., a URI1) for the created resource, where the URI1 is generated by concatenating the child resource identifier 1 subferrionid 1 with the URL1 of the request as a parent resource (parent resource).
For example, the URI1 is { apiRoot }/nnf 2-event-issue/v 1/descriptors id 1.
the second network functional network element assigns an association identification 1(Co-relation ID1) (e.g., a first identification) to the first event subscription. For example, the first identifier is the child resource identifier 1 Suscriptionid 1.
and 403, the second network function network element sends a second request message to the third network function network element, where the second request message is used for requesting a second event subscription from the third network function network element for the first network function network element, and the second request message carries the event identifier and the first identifier.
Specifically, by way of example and not limitation, the second network functional network element determines, according to the Event Id1 carried in the received first Request message, that the first Event subscription requested by the first network functional network element cannot be detected, at this time, the second network functional network element sends an Event open service subscription Request (Nnf3_ Event expose _ Subscribe Request) message (e.g., a second Request message) to the third network functional network element, Nnf3 is a service-based interface presented by the third network functional network element, the second Request message is used for requesting, by the first network functional network element, an Event subscription (e.g., a second Event subscription) to the third network functional network element, and the second Request message is intended to Subscribe, to the third network functional network element, to the second Event provided to the first network functional network element. That is, the second network function network element replaces the first network function network element to perform a second event subscription to the third network function network element, and the first event subscription and the second event subscription carry the same event notification address, that is, the address of the first network function for receiving the event notification. And part or all of the event identifications subscribed to the first event are selected from the event identifications subscribed to the second event. The second request message carries the Event identity Event Id1 together with the first identity.
In addition, the second request message also carries an identifier of the UE to which the first Event subscription is directed, a group identifier of the UE, and an uniform resource locator Nf2Event Notification URL indicating that the first Event subscription is directed to any UE and receiving an Event report.
It should be noted that the first event subscription requested by the first request message and the second event subscription requested by the second request message are both the same event subscription requested by the first network function network element, and the difference is that the first event subscription is subscribed to the second network function network element by the first network function network element through the first request message, and the second event subscription is subscribed to the third network function network element by the second network function network element through the second request message. For example, when the second network function network element fails to detect the first event subscription requested by the first request message, the second network function network element requests the same event subscription (i.e., the second event subscription) as the first event subscription to the third network function network element through the second request message.
In addition, the second request message also carries the requested URL 2. For example, the URL2 for the request is: { apiRoot }/nnf3-event-exposure/v 1/subscriptions/.
404, a third network function network element receives a second request message sent by a second network function network element, where the second request message is used to request a second event subscription from the third network function network element for a first network function network element, the second request message carries an event identifier and a first identifier, the first identifier is an identifier allocated by the second network function network element for a first event subscription, and the first event subscription is an event subscription requested by the first network function network element to the second network function network element.
Specifically, by way of example and not limitation, the third network function network element receives the second request message sent by the second network function network element, creates a resource for the second event subscription according to the information in the second request message, generates a sub-resource identifier 2 (e.g., a subscribentid 2), and constructs a uniform resource locator identifier 2 (e.g., a URI2) for the created resource, where the URI2 is generated by concatenating the sub-resource identifier subscribentied 2 with the URL2 of the request as a parent resource (parent resource).
For example, the URI2 is { apiRoot }/nnf 3-event-issue/v 1/descriptors id 2.
The third network functional network element assigns an association identification 2(Co-relation ID2) to the second event subscription. For example, the association identifier 2 identifies the subscribentid 2 for the child resource.
405, the second network function network element sends a first reply message to the first network function network element, where the first reply message carries a first identifier, and the first identifier is an identifier that is allocated to the first event subscription by the second network function network element.
Specifically, by way of example and not limitation, the second network function network element sends an event open service response (Nnf2_ EventExposure _ subscribe) message (e.g., a first response message) to the first network function network element after assigning the first identifier for the first event subscription, where the Nnf2 is a service-based interface exposed by the second network function network element, and the second response message carries the first identifier.
406, the first network functional network element receives a first response message sent by the second network functional network element, where the first response message carries a first identifier, and the first identifier is an identifier allocated to the first event subscription by the second network functional network element.
Specifically, the first network functional network element receives the first response message sent by the second network functional network element, and acquires the first identifier according to the first response message.
And 407, the third network function network element sends event report information to the first network function network element according to the second request message, where the event report information carries the event identifier and the first identifier.
Specifically, as an example and not by way of limitation, the third network function network element detects an Event matching the Event identifier Event Id1 carried in the second Event subscription, and sends an Event openservice notification Request (Nnf3_ evendexopossures _ Notify Request) message to the first network function network element, where the Nnf3 is a service-based interface presented by the third network function network element, the Event openservice notification Request message carries Event report information for the second Event subscription, and the Event report information carries the Event identifier Event Id1 and the first identifier.
And 408, the first network function network element receives event report information sent by the third network function network element, where the event report information carries the event identifier and the first identifier.
409, the first network function network element determines, based on the first identifier, that the event reporting information is associated with the first event subscription.
Specifically, by way of example and not limitation, the first network function network element receives the event open service notification request message sent by the third network function network element, and receives the first reply message sent by the second network function network element, and determines that the event report information is associated with the first event subscription according to a first identifier carried in the first reply message and the first identifier carried in the event report information.
Thus, by having an intermediate network element (e.g., the second network function network element) generate the association identification in accordance with the event subscription requested by the network element requesting the event subscription (e.g., the first network function network element), and sends the associated identifier (e.g., the first identifier) to the first network function network element and the network element sending the event report (e.g., the third network function network element), and when the third network functional network element receives an event subscription that the second network functional network element requests from the third network functional network element for the first network functional network element, the third network function network element sends the first identifier carried in the event report information to the first network function network element, enabling the first network function network element to determine that the event subscription requested from the second network function network element is associated with the event report information received from the third network function network element according to the association identifier.
As another optional implementation manner, in steps 403, 405, and 406, the second request message sent by the second network function network element to a third network function network element, the event report information sent by the third network function network element to the first network function network element, and the first reply message sent by the second network function network element to the first network function network element carry a second identifier in addition to the first identifier, where the second identifier is used to indicate the second network function network element, and the second identifier may be an identifier (FQDN) or an address (Ipv4 or Ipv 6) of the second network function network element, where the first identifier and the second identifier are associated with a first event subscription, and then the first network function determines, according to the first identifier, that the event report information is associated with the first event subscription, including:
The first network function network element determines that the event report information is associated with the first event subscription according to the first identifier and the second identifier.
In particular, by way of example and not limitation, the first identity assigned by the second network functional network element to the first event subscription may not be unique throughout the communication system.
at this time, the second network function network element is capable of adding a second identifier uniquely identifying the second network function network element to the first reply message and the second request message, sending the second identifier to the first network function network element through the first reply message, sending the second identifier to the third network function network element through the second request message, and sending the second identifier to the first network function network element through event report information by the third network function network element.
When the first network functional network element receives the first reply message and the event reporting information, it is able to determine that the event reporting information is associated with the first event subscription based on the first identity and the second identity in the first reply message and based on the first identity and the second identity in the event reporting information.
Optionally, the second identifier is an IP address of the second network function network element or an FQDN of the second network function network element.
therefore, when the first identifier is not unique, by enabling the second network function network element to provide an identifier (e.g., a second identifier) uniquely indicating the second network function and the first identifier to the first network function network element and the third network function network element, and enabling the third network function network element to send the first identifier and the second identifier to the first network function network element by carrying the first identifier and the second identifier in event report information when the third network function network element receives an event subscription that the second network function network element requests from the third network function network element for the first network function network element, the first network function network element can determine that the event subscription requested from the second network function network element is associated with the event report information received from the third network function network element according to the first identifier and the second identifier.
Fig. 5 is a schematic flow chart of a method 500 for subscribing to an event according to an embodiment of the present application. The method 500 includes at least the following steps.
501, a first network function network element sends a first request message to a second network function network element, where the first request message is used to request a first event subscription from the second network function network element, and the first request message carries an event identifier.
Specifically, by way of example and not limitation, a first network function network element sends an Event open service subscription Request (Nnf2_ eventeExposure _ SubscribeRequest) message (e.g., a first Request message) to a second network function network element, Nnf2 is a service-based interface exposed by the second network function network element, the first Request message carries an Event Id1 (e.g., an Event identifier), and further carries an identifier of a UE for which the first Event subscription is intended, a group identifier of the UE, and a uniform resource locator Nf1Event Notification that indicates that the first Event subscription is for any UE, and that receives an Event report, the first Request message is used for requesting an Event subscription (e.g., a first Event subscription) from the second network function network element.
In addition, the first request message also carries the requested URL 1. For example, the URL1 of the request is that the URL is: { apiRoot }/nnf2-event-exposure/v 1/subscriptions/.
502, a second network function network element receives a first request message sent by a first network function network element, where the first request message is used to request a first event subscription to the second network function network element, and the first request message carries an event identifier.
Specifically, by way of example and not limitation, the second network function network element receives the first request message sent by the first network function network element, creates a resource for the first event subscription according to the information in the first request message, generates a child resource identifier 1 (e.g., a subscriptionid1), and constructs a uniform resource locator identifier 1 (e.g., a URI1) for the created resource, where the URI1 is generated by concatenating the child resource identifier 1 subferrionid 1 with the URL1 of the request as a parent resource (parent resource).
For example, the URI1 is { apiRoot }/nnf 2-event-issue/v 1/descriptors id 1.
The second network functional network element assigns an association identification 1(Co-relation ID1) to the first event subscription. For example, the association identifier 1 identifies 1 subordinate 1 for the child resource.
And 503, the second network function network element sends a second request message to a third network function network element, where the second request message carries the event identifier, and the second request message is used to request a second event subscription to the third network function network element.
Specifically, by way of example and not limitation, the second network functional network element determines, according to the Event Id1 carried in the received first Request message, that the first Event subscription requested by the first network functional network element cannot be detected, at this time, the second network functional network element sends an Event open service subscription Request (Nnf3_ Event expose _ Subscribe) message (e.g., a second Request message) to the third network functional network element, Nnf3 is a service-based interface presented by the third network functional network element, the second Request message is used for requesting an Event subscription (e.g., a second Event subscription) from the third network functional network element to the first network functional network element, and the second Request message is intended to Subscribe to the third network functional network element for the second Event provided to the first network functional network element, that is, the second network functional network element performs a second Event subscription to the third network functional network element in place of the first network functional network element, the second request message carries the Event identification Event Id 1.
It should be noted that the first event subscription requested by the first request message and the second event subscription requested by the second request message are both the same event subscription requested by the first network function network element, and the difference is that the first event subscription is subscribed to the second network function network element by the first network function network element through the first request message, and the second event subscription is subscribed to the third network function network element by the second network function network element through the second request message. For example, when the second network function network element fails to detect the first event subscription requested by the first request message, the second network function network element requests the same event subscription (i.e., the second event subscription) as the first event subscription to the third network function network element through the second request message.
In addition, the second request message also carries an identifier of the UE to which the first Event subscription is directed, a group identifier of the UE, and an uniform resource locator Nf1Event Notification URL indicating that the first Event subscription is directed to any UE and receiving an Event report.
In addition, the second request message also carries the requested URL 2. For example, the URL2 for the request is: { apiRoot }/nnf3-event-exposure/v 1/subscriptions/.
And 504, the third network function network element receives a second request message sent by the second network function network element, where the second request message is used to request the third network function network element for a second event subscription, and the second request message carries an event identifier.
Specifically, by way of example and not limitation, the third network function network element receives the second request message sent by the second network function network element, creates a resource for the second event subscription according to the information in the second request message, generates a sub-resource identifier 2 (e.g., a subscribentid 2), and constructs a uniform resource locator identifier 2 (e.g., a URI2) for the created resource, where the URI2 is generated by concatenating the sub-resource identifier subscribentied 2 with the URL2 of the request as a parent resource (parent resource).
For example, the URI2 is { apiRoot }/nnf 3-event-issue/v 1/descriptors id 2.
The third network functional network element assigns an association identification 2(Co-relation ID2) to the second event subscription. For example, the association identifier 2 identifies the subscribentid 2 for the child resource.
And 505, the third network function network element sends a second response message to the second network function network element according to the second request message, where the second response message carries a third identifier, and the third identifier is an identifier allocated to the second event subscription by the third network function network element.
Specifically, by way of example and not limitation, after allocating the association identifier 2 to the second event subscription, the third network function network element sends an event open service response (Nnf3_ EventExposure _ subscribe response) message (e.g., a second response message) to the second network function network element, where the Nnf3 is a service-based interface exposed by the third network function network element, and the second response message carries the association identifier 2 (e.g., a third identifier).
And 506, the second network function network element receives a second response message sent by a third network function network element, where the second response message carries a third identifier, and the third identifier is an identifier allocated by the third network function network element for the second event subscription.
specifically, as an example and not by way of limitation, the second network function network element receives the second response message sent by the third network function network element, and acquires the third identifier according to the second response message.
507, the second network function network element sends a first reply message to the first network function network element, where the first reply message carries the third identifier.
Specifically, by way of example and not limitation, after the second network function network element receives the first request message sent by the first network function network element, the second network function network element sends an event open service Response (Nnf2_ EventExposure _ Subscribe Response) message (e.g., a first Response message) to the first network function network element, Nnf2 is a service-based interface exposed by the third network function network element, and the first Response message carries the third identifier.
In addition, as an example and not by way of limitation, the first reply message sent by the second network function network element to the first network function may also carry the Co-relation ID1 allocated by the second network function for the first event subscription in step 502, in addition to the third identifier.
And 508, the first network functional network element receives a first response message sent by the second network functional network element, where the first response message carries a third identifier, the third identifier is an identifier allocated by the third network functional network element for a second event subscription, and the second event subscription is an event subscription requested by the second network functional network element to the third network functional network element.
Specifically, as an example and not by way of limitation, the first network function network element receives the first reply message sent by the second network function network element, and acquires the third identifier according to the first reply message.
509, the third network function network element sends event report information to the first network function network element, where the event report information carries the event identifier and the third identifier.
Specifically, as an example and not by way of limitation, the third network function network element detects an Event matching the Event identifier Event Id1 carried in the second Event subscription, and sends an Event openness service notification Request (Nnf3_ evendexopossure _ Notify Request) message to the first network function network element, where the Nnf3 is a service-based interface presented by the third network function network element, the Event openness service notification Request message carries Event report information for the second Event subscription, the Event report information carries the Event identifier Event Id1 and the third identifier, and the nf3 is a service-based interface presented by the third network function network element.
And 510, the first network function network element receives event report information sent by the third network function network element, where the event report information carries the event identifier and the third identifier.
The first network function network element determines, based on the third identifier, that the event reporting information is associated with the first event subscription 511.
Specifically, by way of example and not limitation, the first network function network element receives the event open service notification request message sent by the third network function network element, and receives the first reply message sent by the second network function network element, and determines that the event report information is associated with the first event subscription according to a third identifier carried in the first reply message and the third identifier carried in the event report information.
Therefore, by enabling the third network function network element to generate the association identifier when receiving the event subscription that the second network function network element requests from the third network function network element for the first network function network element, and sending the association identifier (for example, the third identifier) to the second network function network element, the second network function network element sends the third identifier to the first network function network element, and enables the third network function network element to carry the third identifier in the event report information and send the event report information to the first network function network element, the first network function network element can determine, according to the third identifier, that the event subscription requested from the second network function network element is associated with the event report information received from the third network function network element.
As another optional implementation manner, in steps 505, 507 and 509, the second response message sent by the third network functional network element to the second network functional network element, the first response message sent by the second network functional network element to the first network functional network element, and the event report information sent by the third network functional network element to the first network functional network element carry a fourth identifier in addition to the third identifier, where the fourth identifier is used to indicate the third network functional network element, and the third identifier and the fourth identifier are used to be associated with a first event subscription, and then the determining, by the first network functional network element, that the event report information is associated with the first event subscription according to the third identifier includes:
The first network function network element determines that the event report information is associated with the first event subscription according to the third identifier and the fourth identifier.
In particular, by way of example and not limitation, the third identity assigned by the third network functional network element to the second event subscription may not be unique throughout the communication system.
At this time, the third network function network element is capable of adding a fourth identifier uniquely identifying the third network function network element to the first reply message and the event report information, sending the fourth identifier to the first network function network element through the event report information, sending the fourth identifier to the second network function network element through the first reply message, and sending the fourth identifier to the first network function network element through the first reply message by the second network function network element.
When the first network functional network element receives the first reply message and the event reporting information, it is able to determine that the event reporting information is associated with the first event subscription according to the third identity and the fourth identity in the first reply message and according to the third identity and the fourth identity in the event reporting information.
Optionally, the fourth identifier is an IP address of the third network function network element or an FQDN of the third network function network element.
Thus, when the third identifier is not unique, the first network function network element can determine that the event subscription requested to the second network function network element is associated with the event report information received from the third network function network element according to the third identifier and the fourth identifier by causing the third network function network element to send an identifier (e.g., a fourth identifier) uniquely indicating the third network function network element and the third identifier to the second network function network element, sending the fourth identifier and the third identifier to the first network function network element by the second network function network element, and causing the third network function network element to send the fourth identifier and the third identifier to the first network function network element in the event report information.
In order to better understand the method for subscribing to an event provided by the present application, the first network functional network element is the NEF network element 170 in fig. 1, the second network functional network element is the UDM network element 190 in fig. 1, and the third network functional network element may be the AMF network element 150 in fig. 1; alternatively, the first network functional network element may be the NEF network element 170 in fig. 1, the second network functional network element may be the PCF network element 180 in fig. 1, and the third network functional network element may be the SMF network element 160 in fig. 1 as an example, which will describe in detail the method for subscribing to the event provided by the present application.
The method 400 for subscribing to an event provided by the present application is further described in detail with reference to the method 600 shown in fig. 6, taking the first network functional network element as the NEF network element 170 in fig. 1, the second network functional network element as the UDM network element 190 in fig. 1, and the third network functional network element as the AMF network element 150 in fig. 1 as an example. The method comprises at least the following steps.
601, the NEF network element receives the trigger and decides to subscribe the event to the UDM network element. The trigger may be from other NF network elements (e.g., AF network elements) or internal, where the trigger from the AF network element may be that the AF network element performs event subscription with the NEF network element.
602, the NEF network element sends an event open service subscription Request, numdm _ EventExposure _ Subscribe Request message, to the UDM network element, where the numdm _ EventExposure _ Subscribe Request message is used to Request a first event subscription from the UDM network element, and numdm is a service-based interface presented by the UDM network element.
Specifically, by way of example and not limitation, the NEF network element sends an HTTP POST message to the UDM network element, where an Event identifier Event Id1 corresponding to the first Event subscription and a uniform resource locator neffevent Notification URL of the received Event report are carried in a message body of the HTTP POST message, and the Event Id1 may be a list of one or more events.
In addition, the HTTP POST message also carries any one of an identifier of the UE to which the first event subscription is directed, a group identifier of the UE, and indication information indicating that the first event subscription is directed to any UE.
In addition, the HTTP POST message also carries the URL1 of the request. For example, the URL1 for the request is: { apiRoot }/numm-event-exposure/v 1/subscriptions/.
603, the UDM element stores the subscription information and assigns an association ID Co-relation ID1 for the subscription of the first event from the NEF element.
Specifically, as an example and not by way of limitation, the UDM network element subscribes to create a resource for a first event according to information carried in a message body of the HTTP POST message, generates a child resource identifier 1 (e.g., a subscriptionid1), and constructs a uniform resource locator identifier 1 (e.g., a URI1) for the created resource, where the URI1 is generated by using the URL1 of the request as a parent resource (parent resource) and then concatenating the child resource identifier 1 subfcriptionid 1.
For example, the URI1 is { apiRoot }/numm-event-issue/v 1/descriptions id 1.
The UDM network element assigns an association identity 1(Co-relation ID1) to the first event subscription. For example, the association identifier 1 identifies 1 subordinate 1 for the child resource.
604, if the UDM network element determines that the event carried in the event identifier Evnet Id1 cannot be detected, the UDM network element sends an event open service subscription Request (Namf _ eventxonsource _ Subscribe Request) message to the AMF network element, where the Namf _ eventxonsource _ Subscribe Request message is used to Request a second event subscription to the AMF network element, the Namf _ eventxonsource _ Subscribe Request message carries Co-relation Id1, and Namf is a service-based interface displayed by the AMF network element.
Specifically, by way of example and not limitation, the UDM network element sends an HTTP POST message to the AMF network element, where a subscriptionid1, an Event identifier Event Id1 corresponding to the second Event subscription, and a uniform resource locator neffevent Notification URL of receiving an Event report are carried in a message body of the HTTP POST message, and the Event Id1 may be a list of one or more events.
In addition, the HTTP POST message also carries any one of an identifier of the UE to which the second event subscription is directed, a group identifier of the UE, and indication information indicating that the second event subscription is directed to any UE.
In addition, the HTTP POST message also carries the URL2 of the request. For example, the URL2 for the request is: { apiRoot }/namf-event-exposure/v 1/subscriptions/.
It should be noted that the first event subscription requested by the numf _ EventExposure _ Subscribe message and the second event subscription requested by the Namf _ EventExposure _ Subscribe message are the same event subscription requested by the NEF element, and the difference is that the first event subscription is subscribed to the UDM element by the NEF element through the numf _ EventExposure _ Subscribe message, and the second event subscription is subscribed to the AMF element by the UDM element through the Namf _ EventExposure _ Subscribe message. For example, when the UDM network element fails to detect the first event subscription requested by the Nudm _ EventExposure _ Subscribe Request message, the UDM network element requests the same event subscription (i.e., the second event subscription) as the first event subscription from the AMF network element through a Namf _ EventExposure _ Subscribe message.
605 the AMF element stores the subscription information and assigns an association ID Co-relation ID2 for the second event subscription from the UDM element.
Specifically, as an example and not by way of limitation, the AMF network element creates a resource for the second event subscription according to the information carried in the message body of the HTTP POST message, generates a sub-resource identifier 2 (e.g., a subscriptionid2), and constructs a uniform resource locator identifier 2 (e.g., a URI2) for the created resource, where the URI2 is generated by using the URL2 of the request as a parent resource (parent resource) and splicing the sub-resource identifier 2subscriptionid 2.
For example, the URI2 is { apiRoot }/namf-event-issue/v 1/descriptions id 2.
The AMF network element allocates an association ID 2(Co-relation ID2) to the second event subscription. For example, the association identifier 2 is the child resource identifier 2 substinguistionid 2.
606, the AMF network element sends an event open service Response (Namf _ EventExposure _ Subscribe Response) message to the UDM network element, which carries Co-relationship id 2.
Specifically, by way of example and not limitation, the AMF network element sends an HTTP Response message to the UDM network element, the HTTP Response message including a Status Code (Status Code)201Created, a header field (header), and a message body. The URI2 generated in step 605 is carried in the header field, and the status code "201 Created" indicates that the subscription of the second event of the UDM network element is successful.
Optionally, the Co-relation ID2 carried in the message body is a subscriptionid 2.
607, the UDM network element sends an event open service Response (numdm _ EventExposure _ Subscribe Response) message to the NEF network element, which carries the Co-relationship id 1.
Specifically, by way of example and not limitation, the UDM network element sends an HTTP Response message to the NEF network element, the HTTP Response message including a Status Code 201Created, a header field (header), and a message body. The URI1 generated in step 603 is carried in the header field, and the status code "201 Created" indicates that the subscription of the first event of the NEF element is successful.
Optionally, the Co-relation ID1 carried in the message body is a subscriptionid 1.
The AMF network element detects 608 an Event that can be monitored by the AMF network element and matches the Event Id 1.
609, the AMF network element sends an event open service notification Request (Namf _ EventExposure _ Notify Request) message to the NEF network element, where the Namf _ EventExposure _ Notify Request message carries event report information and Co-relation ID1 for the second event subscription of the UDM network element.
specifically, by way of example and not limitation, the AMF network element sends an HTTP POST message to the NEF network element, where a message body of the HTTP POST message carries Event Id1 and subscriptionid1 detected by the AMF network element. And the Namf is a service-based interface displayed by the AMF network element.
The NEF network element sends an event open service notification Response (Namf _ EventExposure _ Notify Response) message to the AMF network element 610.
Specifically, as an example and not by way of limitation, the NEF network element determines that the event report information carried in the Namf _ EventExposure _ notification Request message in step 609 is associated with the first event subscription according to the Co-relation ID1 carried in the Namf _ EventExposure _ notification Request message in step 609 and the Co-relation ID1 carried in the numdm _ EventExposure _ Subscribe Response message in step 607.
More specifically, when the Co-relation ID1 is a subscriptionId1, the NEF network element determines that the event report information carried in the POST message of step 609 is associated with the first event subscription according to the subscriptionId1 carried in the HTTP POST message of step 609 and the subscriptionId1 carried in the HTTP Response message of step 607.
And the NEF network element sends an HTTP Response message to the AMF network element, wherein the HTTP Response message carries a Status Code (Status Code)200OK, and the 200OK indicates that the Namf _ EventExposure _ Notify Request message returned by the AMF network element is successfully received.
As another optional implementation manner, in steps 604, 607 and 609, the Namf _ EventExposure _ Subscribe Request message sent by the UDM network element to an AMF network element, the numdm _ EventExposure _ Subscribe Response message sent by the UDM network element to a NEF network element, and the Namf _ EventExposure _ Notify Request message sent by the AMF network element to the NEF network element carry, in addition to the Co-relation ID1, an UDM network element identifier (UDM ID), where the UDM ID indicates the UDM network element, and then the NEF network element determines that the event report information is associated with the first event subscription according to the Co-relation ID1, including:
The NEF network element determines that the event report information is associated with the first event subscription according to the Co-relation ID1 and the UDM ID.
In particular, by way of example and not limitation, the Co-relation ID1 assigned by the UDM network element for the first event subscription may not be unique throughout the communication system.
At this time, the UDM network element adds an UDM ID capable of uniquely identifying the UDM network element to the Nudm _ EventExposure _ Subscribe Response message and the Namf _ EventExposure _ Subscribe Request message, transmits the UDM ID to the NEF network element through the Nudm _ EventExposure _ Subscribe Response message, and transmits the UDM ID to the AMF network element through the Namf _ EventExposure _ Subscribe Request message, and the AMF network element transmits the UDM ID to the NEF network element through the Namf _ EventExposure _ Notify Request message.
When the NEF element receives the numf _ EventExposure _ Subscribe Response message and the Namf _ EventExposure _ Notify Request message, it is able to determine that the event report information is associated with the first event subscription based on the Co-relation ID1 and the UDM ID in the numf _ EventExposure _ Subscribe Response message and based on the Co-relation ID1 and the UDM ID in the Namf _ EventExposure _ Notify Request message.
Optionally, the UDM ID is an IP address of the UDM network element or an FQDN of the UDM network element.
Taking the first network functional network element as the NEF network element 170 in fig. 1, the second network functional network element as the UDM network element 190 in fig. 1, and the third network functional network element as the AMF network element 150 in fig. 1 as an example, the method 500 for subscribing to an event provided by the present application is further described in detail with reference to the method 700 shown in fig. 7. The method comprises at least the following steps.
701, the NEF network element receives the trigger and decides to subscribe the event to the UDM network element. The trigger may be from other NF network elements (e.g., AF network elements) or internal, where the trigger from the AF network element may be that the AF network element performs event subscription with the NEF network element.
702, the NEF network element sends an event open service subscription Request, numdm _ EventExposure _ Subscribe Request, message to the UDM network element, where the numdm _ EventExposure _ Subscribe Request message is used to Request a first event subscription from the UDM network element, and numdm is a service-based interface presented by the UDM network element.
Specifically, by way of example and not limitation, the NEF network element sends an HTTP POST message to the UDM network element, where an Event identifier Event Id1 corresponding to the first Event subscription and a uniform resource locator neffevent Notification URL of the received Event report are carried in a message body of the HTTP POST message, and the Event Id1 may be a list of one or more events.
In addition, the HTTP POST message also carries any one of an identifier of the UE to which the first event subscription is directed, a group identifier of the UE, and indication information indicating that the first event subscription is directed to any UE.
In addition, the HTTP POST message also carries the URL1 of the request. For example, the URL1 for the request is: { apiRoot }/numm-event-exposure/v 1/subscriptions/.
703, the UDM element stores the subscription information and assigns an association ID 1(Co-relation ID1) to the subscription of the first event from the NEF element.
Specifically, as an example and not by way of limitation, the UDM network element subscribes to create a resource for a first event according to information carried in a message body of the HTTP POST message, generates a child resource identifier 1 (e.g., a subscriptionid1), and constructs a uniform resource locator identifier 1 (e.g., a URI1) for the created resource, where the URI1 is generated by using the URL1 of the request as a parent resource (parent resource) and then concatenating the child resource identifier 1 subfcriptionid 1.
For example, the URI1 is { apiRoot }/numm-event-issue/v 1/descriptions id 1.
The UDM network element assigns an association identity 1(Co-relation ID1) to the first event subscription. For example, the association identifier 1 identifies 1 subordinate 1 for the child resource.
704, if the UDM network element determines that the event carried in the event identifier Evnet Id1 cannot be detected, the UDM network element sends an event open service subscription Request (Namf _ evendexposure _ Subscribe Request) message to the AMF network element, where the Namf _ evendexposure _ Subscribe Request message is used to Request a second event subscription to the AMF network element, and the Namf is a service-based interface displayed by the AMF network element.
Specifically, by way of example and not limitation, the UDM network element sends an HTTP POST message to the AMF network element, where an Event identifier Event Id1 corresponding to the second Event subscription and a uniform resource locator neffevent Notification URL for receiving an Event report are carried in a message body of the HTTP POST message, and the Event Id1 may be a list of one or more events.
In addition, the HTTP POST message also carries any one of an identifier of the UE to which the second event subscription is directed, a group identifier of the UE, and indication information indicating that the second event subscription is directed to any UE.
In addition, the HTTP POST message also carries the URL2 of the request. For example, the URL2 for the request is: { apiRoot }/namf-event-exposure/v 1/subscriptions/.
it should be noted that the first event subscription requested by the numf _ EventExposure _ Subscribe message and the second event subscription requested by the Namf _ EventExposure _ Subscribe message are the same event subscription requested by the NEF element, and the difference is that the first event subscription is subscribed to the UDM element by the NEF element through the numf _ EventExposure _ Subscribe message, and the second event subscription is subscribed to the AMF element by the UDM element through the Namf _ EventExposure _ Subscribe message. For example, when the UDM network element fails to detect the first event subscription requested by the Nudm _ EventExposure _ Subscribe Request message, the UDM network element requests the same event subscription (i.e., the second event subscription) as the first event subscription from the AMF network element through a Namf _ EventExposure _ Subscribe message.
705, the AMF element stores the subscription information and assigns an association ID Co-relation ID2 for the second event subscription from the UDM element.
Specifically, as an example and not by way of limitation, the AMF network element creates a resource for the second event subscription according to the information carried in the message body of the HTTP POST message, generates a sub-resource identifier 2 (e.g., a subscriptionid2), and constructs a uniform resource locator identifier 2 (e.g., a URI2) for the created resource, where the URI2 is generated by using the URL2 of the request as a parent resource (parent resource) and splicing the sub-resource identifier 2subscriptionid 2.
For example, the URI2 is { apiRoot }/namf-event-issue/v 1/descriptions id 2.
The AMF network element allocates an association ID 2(Co-relation ID2) to the second event subscription. For example, the association identifier 2 is the child resource identifier 2 substinguistionid 2.
At 706, the AMF element sends an event open service Response (Namf _ EventExposure _ Subscribe Response) message to the UDM element, where the Namf _ EventExposure _ Subscribe Response message carries Co-relationship id 2.
Specifically, by way of example and not limitation, the AMF network element sends an HTTP Response message to the UDM network element, the HTTP Response message including a Status Code (Status Code)201Created, a header field (header), and a message body. Wherein, the URI2 generated in step 705 is carried in the header field, and the status code "201 Created" indicates that the subscription of the second event of the UDM network element is successful.
Optionally, the Co-relation ID2 carried in the message body is a subscriptionid 2.
707, the UDM network element sends an event open service Response (numdm _ EventExposure _ Subscribe Response) message to the NEF network element, the numdm _ EventExposure _ Subscribe Response message carrying the Co-relationship id 2.
specifically, by way of example and not limitation, the UDM network element sends an HTTP Response message to the NEF network element, the HTTP Response message including a Status Code 201Created, a header field (header), and a message body. Wherein, the header field carries the URI1 generated in step 703, the message body carries the subscriptionid2 (as an example of Co-relation ID2), and the status code "201 Created" indicates that the subscription of the first event of the NEF element is successful.
In addition, as an example and not by way of limitation, in addition to carrying the subscriptionid2, the message body of the HTTP Response message sent by the UDM network element to the NEF network element may also carry a Co-relation ID1 allocated by the UDM network element for the subscription of the first event in step 703.
the AMF network element detects an Event that can be monitored by the AMF network element and matches Event Id1 708.
709, the AMF network element sends an event open service notification Request (Namf _ EventExposure _ Notify Request) message to the NEF network element, where the Namf _ EventExposure _ Notify Request message carries event report information for a second event subscription of the UDM network element, and the Namf _ EventExposure _ Notify Request message carries Co-relation ID 2.
Specifically, by way of example and not limitation, the AMF network element sends an HTTP POST message to the NEF network element, where a message body of the HTTP POST message carries Event Id1 and subscriptionid2 detected by the AMF network element. And the Namf is a service-based interface displayed by the AMF network element.
710, the NEF network element sends an event open service notification Response (Namf _ EventExposure _ Notify Response) message to the AMF network element.
Specifically, as an example and not by way of limitation, the NEF network element determines that the event report information carried in the Namf _ EventExposure _ notification Request message in step 709 is associated with the first event subscription according to the Co-relation ID2 carried in the Namf _ EventExposure _ notification Request message in step 709 and the Co-relation ID2 carried in the numdm _ EventExposure _ Subscribe Response message in step 707.
more specifically, when the Co-relation ID2 is a subscriptionid2, the NEF network element determines that the event report information carried in the HTTP POST message in step 709 is associated with the first event subscription according to the subscriptionid2 carried in the HTTP POST message in step 709 and the subscriptionid2 carried in the HTTP Response message in step 707.
And the NEF network element sends HTTP Response message to the AMF network element, wherein the HTTP Response message carries Status Code (Status Code)200OK, and the 200OK indicates successful receiving of HTTP POST message sent by the AMF network element.
As another optional implementation manner, in steps 706, 707 and 710, the Namf _ EventExposure _ Subscribe Response message sent by the AMF network element to an UDM network element, the Nudm _ EventExposure _ Subscribe Response message sent by the UDM network element to a NEF network element, and the Namf _ EventExposure _ Notify Request message sent by the AMF network element to the NEF network element carry an AMF network element identifier (AMF ID) in addition to the Co-relation ID2, where the AMF ID indicates the AMF network element, and then the NEF network element determines that the event report information is associated with the first event subscription according to the Co-relation ID2, including:
The NEF network element determines that the event report information is associated with the first event subscription based on the Co-relation ID2 and the AMF ID.
In particular, by way of example and not limitation, the Co-relation ID2 assigned by the AMF network element for the second event subscription may not be unique throughout the communication system.
At this time, the AMF element adds the AMF ID capable of uniquely identifying the AMF element to the Namf _ EventExposure _ Subscribe Response message and the Namf _ EventExposure _ Notify Request message, transmits the AMF ID to the NEF element through the Namf _ EventExposure _ Notify Request message, transmits the AMF ID to the UDM element through the Namf _ EventExposure _ Subscribe Response message, and transmits the AMF ID to the NEF element through the UDM element through the Nudm _ EventExposure _ Subscribe Response message.
When the NEF element receives the numf _ EventExposure _ Subscribe Response message and the Namf _ EventExposure _ Notify Request message, it is able to determine that the event report information is associated with the first event subscription according to the Co-relation ID2 and the AMF ID in the numf _ EventExposure _ Subscribe Response message, and according to the Co-relation ID2 and the AMF ID in the Namf _ EventExposure _ Notify Request message.
Optionally, the AMF ID is an IP address of the AMF network element or an FQDN of the AMF network element.
Taking the first network functional network element as the NEF network element 170 in fig. 1, the second network functional network element as the PCF network element 180 in fig. 1, and the third network functional network element may be the SMF network element 160 in fig. 1 as an example, the method 400 for subscribing to an event provided by the present application is further described in detail with reference to the method 800 shown in fig. 8. The method comprises at least the following steps.
The NEF network element receives 801 a trigger, possibly from another NF network element (e.g. an AF network element) or internally, deciding to request policy authorization from the PCF network element. The trigger from the AF network element may be policy authorization from the AF network element to the NEF network element.
802, the NEF network element sends a policy authorization creation Request (Npcf _ PolicyAuthorization _ Create Request) message to the PCF network element, the Npcf _ PolicyAuthorization _ Create Request message carries application layer information, and the application layer information is used for requesting policy authorization. Wherein, the Npcf is a service-based interface displayed by the PCF network element.
Specifically, as an example and not by way of limitation, the NEF network element sends an HTTP POST message to the PCF network element, where the message body of the HTTP POST message carries application layer information.
in addition, the HTTP POST message also carries the URL1 of the request. For example, the URL1 for the request is: { apiRoot }/npcf-poliomyhoiation/v 1/app-sessions/.
803, the PCF network element saves the information and creates an application session context.
Specifically, as an example and not by way of limitation, the PCF network element creates a resource for the application session according to the information carried in the message body of the HTTP POST message in step 802, generates a sub-resource identifier 1 appessionid, and constructs a URI1 for this created resource. The URI1 is generated using the URL1 of the request as the parent resource (parent resource) and concatenating the child resource identification 1 appessionid.
for example, the URI1 is { apiRoot }/npcf-polirecognition/v 1/app-sessions/appessionid/.
At 804, the PCF network element sends a policy authorization creation Response (Npcf _ PolicyAuthorization _ Create Response) message to the NEF network element.
Specifically, by way of example and not limitation, the PCF network element sends an HTTP Response message to the NEF network element, the HTTP Response message including a Status Code 201Created, a header field (header), and a message body. The URI1 generated in step 805 is carried in the header field, and the status code "201 Created" indicates that the NEF element successfully requests the policy authorization creation.
Optionally, the appessionid is carried in the message body.
805, after performing policy decision according to the application layer information, the network policy, and the user signing convention, the PCF network element sends a Session Management (SM) policy update notification Request (Npcf _ SMPolicy _ UpdateNotify Request) message to the SMF network element, where the Npcf _ SMPolicy _ UpdateNotify Request message carries the formulated policy, including the PCC rule.
Specifically, as an example and not by way of limitation, the PCF network element sends an HTTP POST message to the SMF network element, where a message body of the HTTP POST message carries the formulated policy.
In addition, the HTTP POST message also carries a URL2 of the request, where the URL2 is an Update Notification (Update Notification) URL, the URL2 is provided by the SMF network element to the PCF network element when the SMF network element interacts with the PCF network element before, and the URL2 is used for policy Notification.
806, after the SMF network element saves the policy decision, it sends a session management policy update notification Response (Npcf _ SMPolicy _ UpdateNotify Response) message to the PCF network element.
Specifically, by way of example and not limitation, the SMF network element sends an HTTP Response message to the PCF network element, where the HTTP Response message includes a Status Code (Status Code)200OK, and the Status Code "200 OK" indicates that the SMF network element successfully receives the Npcf _ SMPolicy _ UpdateNotify Request message sent by the PCF network element.
807, the NEF network element receives a trigger that requires an event subscription for the application session.
808, the NEF network element sends a policy authorization subscription Request (Npcf _ PolicyAuthorization _ Subscribe Request) message to the PCF network element, where the Npcf _ PolicyAuthorization _ Subscribe message is used to Request a first event subscription from the PCF network element, and the Npcf is a service-based interface exhibited by the PCF network element.
specifically, as an example and not by way of limitation, the NEF network element sends HTTP PATCH a message to the PCF network element, where a message body of the HTTP PATCH message carries an appessentid and an Event identity Event Id1 corresponding to the first Event subscription, and the NEF network element assigns the appessentid carried in the HTTP Response message in step 804 as an association identity 1(Co-relation Id1) assigned to the first Event subscription by the PCF network element.
In addition, the HTTP PATCH message also carries the requested URL 2. For example, the URL2 for the request is: { apiRoot }/npcf-poliomyhoiation/v 1/app-sessions/appessionid/.
The PCF network element saves the subscription information, updates the application session context and adds the Event identification Event Id1 at 809.
Specifically, by way of example and not limitation, the first event subscription is added to the resource created in step 803, i.e.,
The first Event is added to subscribe to the corresponding Event identification Event Id 1.
The PCF network element sends a policy authorization subscription answer (Npcf _ PolicyAuthorization _ subscription Response) message to the NEF network element 810.
Specifically, by way of example and not limitation, the PCF network element sends an HTTP Response message to the NEF network element, the HTTP Response message including a Status Code (Status Code)200OK, the Status Code "200 OK" indicating that the NEF network element successfully completed the first event subscription.
811, the PCF network element sends an open event service subscription Request (Nsmf _ EventExposure _ Subscribe Request) message to the SMF network element, where the Nsmf _ EventExposure _ Subscribe Request message is used to Request a second event subscription to the SMF network element, and the Nsmf _ EventExposure _ Subscribe Request message carries Co-relation ID1 (e.g., appserviceid), and the Nsmf is a service-based interface exhibited by the SMF network element.
specifically, as an example and not by way of limitation, the PCF network element sends an HTTP POST message to the SMF network element, where an appessionid, an Event identifier Event Id1 corresponding to the second Event subscription, and a uniform resource locator neffevent Notification URL of the received Event report are carried in a message body of the HTTP POST message, and the Event Id1 may be a list of one or more events.
In addition, the HTTP POST message also carries any one of an identifier of the UE to which the second event subscription is directed, a group identifier of the UE, and indication information indicating that the second event subscription is directed to any UE.
In addition, the HTTP POST message also carries the URL3 of the request. For example, the URL3 for the request is:
{ apiRoot }/nsmf-event-exposure/v 1/subscriptions/. It is noted that
The first event subscription requested by the Npcf _ PolicyAuthorization _ Subscribe message and the second event subscription requested by the Nsmf _ EventExposure _ Subscribe message are the same event subscription requested by the NEF network element, except that the first event subscription is subscribed to the PCF network element by the NEF network element through the Npcf _ PolicyAuthorization _ Subscribe message, and the second event subscription is subscribed to the SMF network element by the PCF network element through the Nsmf _ EventExposure _ Subscribe message. For example, when the PCF network element is unable to detect the first event subscription requested by the Npcf _ PolicyAuthorization _ subscription message, the PCF network element requests the SMF network element for the same event subscription (i.e., the second event subscription) as the first event subscription through the Nsmf _ EventExposure _ subscription message.
The SMF network element stores 812 the subscription information and assigns 2 a Co-relation ID for the second event subscription from the PCF network element.
specifically, as an example and not by way of limitation, the SMF network element creates a resource for the second event subscription according to the information carried in the message body of the HTTP POST message, generates a sub-resource identifier 2 (e.g., a subscriptionid2), and constructs a uniform resource locator identifier 2 (e.g., a URI2) for the created resource, where the URI2 is generated by concatenating the sub-resource identifier 2subscriptionid2 with the URL3 of the request as a parent resource (parent resource).
for example, the URI2 is { apiRoot }/nsmf-event-issue/v 1/descriptions id 2.
The SMF network element assigns an association identification 2(Co-relation ID2) to the second event subscription. For example, the association identifier 2 is the child resource identifier 2 substinguistionid 2.
813, the SMF network element returns an event open service subscription Response (Nsmf _ EventExposure _ Subscribe Response) message to the PCF network element, where the Nsmf _ EventExposure _ Subscribe Response message carries the Co-relation ID 2.
Specifically, by way of example and not limitation, the SMF network element sends an HTTP Response message to the PCF network element, the HTTP Response message including a Status Code 201Created, a header field (header), and a message body. The URI2 generated in step 802 is carried in the header field, and the status code "201 Created" indicates that the second event subscription of the PCF network element is successful.
Optionally, the Co-relation ID2 carried in the message body is a subscriptionid 2.
814, the SMF network element detects an Event that can be monitored by the SMF network element and matches the Event Id 1.
815, the SMF network element sends an event open service notification Request (Nsmf _ EventExposure _ Notify Request) message to the NEF network element, where the Nsmf _ EventExposure _ Notify Request message carries event report information and Co-relation ID1 for a second event subscription of the PCF network element.
Specifically, by way of example and not limitation, the SMF network element sends an HTTP POST message to the NEF network element, where a message body of the HTTP POST message carries the Event Id1 and the appessionid detected by the SMF network element. Wherein the Nsmf is a service-based interface displayed by the SMF network element.
816, the NEF network element sends an event open service notification Response (Nsmf _ EventExposure _ Notify Response) message to the SMF network element.
Specifically, as an example and not by way of limitation, the NEF network element determines that the event report information carried in the Nsmf _ EventExposure _ notification Request message in step 815 is associated with the first event subscription according to the Co-relation ID1 carried in the Nsmf _ EventExposure _ notification Request message in step 815 and the Co-relation ID1 carried in the Npcf _ policy authorization _ Create Response message in step 804.
more specifically, when the Co-relation ID1 is an appessionid, the NEF network element determines that the event report information carried in the Nsmf _ EventExposure _ notification Request message in step 815 is associated with the first event subscription according to the appessionid carried in the HTTP POST message in step 815 and the appessionid carried in the HTTP Response message in step 804. And the NEF network element sends an HTTP Response message to the SMF network element, wherein the HTTP Response message carries a Status Code (Status Code)200OK, and the 200OK indicates that the Nsmf _ EventExposure _ Notify Request message returned by the SMF network element is successfully received.
as another optional implementation manner, in steps 804, 811, and 814, the Npcf _ PolicyAuthorization _ Create Response message sent by the PCF network element to the NEF network element, the Nsmf _ EventExposure _ Subscribe Request message sent by the PCF network element to the SMF network element, and the Nsmf _ EventExposure _ Notify Request message sent by the SMF network element to the NEF network element carry a network element identifier (PCF ID) in addition to the apssossid, where the PCF ID indicates the PCF network element, and then the NEF network element determines that the event report information is associated with the first event subscription according to the apssossid, including:
The NEF network element determines that the event report information is associated with the first event subscription according to the appessionid and the PCF ID.
Specifically, by way of example and not limitation, the appessionid assigned by the PCF network element for the first event subscription may not be unique throughout the communication system.
At this time, the PCF network element adds the PCF ID capable of uniquely identifying the PCF network element to the Npcf _ PolicyAuthorization _ Create Response message and the Nsmf _ EventExposure _ Subscribe Request message, transmits the PCF ID to the NEF network element through the Npcf _ PolicyAuthorization _ Create Response message, transmits the PCF ID to the SMF network element through the Nsmf _ EventExposure _ Subscribe Request, and transmits the PCF ID to the NEF network element through the Nsmf _ EventExposure _ Notify Request message.
When the NEF network element receives the Npcf _ PolicyAuthorization _ Create Response message and the Nsmf _ EventExposure _ Notify Request message, it can determine that the event report information is associated with the first event subscription according to the appessonid and the PCF ID in the Npcf _ PolicyAuthorization _ Create Response message and according to the appessonid and the PCF ID in the Nsmf _ EventExposure _ Notify Request message.
Optionally, the PCF ID is an IP address of the PCF network element or an FQDN of the PCF network element.
Taking the first network functional network element as the NEF network element 170 in fig. 1, the second network functional network element as the PCF network element 180 in fig. 1, and the third network functional network element may be the SMF network element 160 in fig. 1 as an example, the method 500 for subscribing to an event provided by the present application is further described in detail with reference to the method 900 shown in fig. 9. The method comprises at least the following steps.
The NEF element receives a trigger, which may be from another NF element (e.g., an AF element) or internal, to request policy authorization from the PCF element 901. The trigger from the AF network element may be policy authorization from the AF network element to the NEF network element.
902, the NEF network element sends a policy authorization creation Request (Npcf _ PolicyAuthorization _ Create Request) message to the PCF network element, where the Npcf _ PolicyAuthorization _ Create Request message carries application layer information, and the application layer information is used for requesting policy authorization. Wherein, the Npcf is a service-based interface displayed by the PCF network element.
Specifically, as an example and not by way of limitation, the NEF network element sends an HTTP POST message to the PCF network element, where the message body of the HTTP POST message carries application layer information.
In addition, the HTTP POST message also carries the URL1 of the request. For example, the URL1 for the request is: { apiRoot }/npcf-poliomyhoiation/v 1/app-sessions/.
The PCF network element saves the information and creates an application session context 903.
Specifically, as an example and not by way of limitation, the PCF network element creates a resource for the application session according to the information carried in the message body of the HTTP POST message in step 902, generates a sub-resource identifier 1 (appessionid), and constructs a URI1 for this created resource. The URI1 is generated using the URL1 of the request as the parent resource (parent resource) and concatenating the child resource identification 1 appessionid.
For example, the URI1 is { apiRoot }/npcf-polirecognition/v 1/app-sessions/appessionid.
904, the PCF network element sends a policy authorization creation Response (Npcf _ PolicyAuthorization _ Create Response) message to the NEF network element.
Specifically, by way of example and not limitation, the PCF network element sends an HTTP Response message to the NEF network element, the HTTP Response message including a Status Code 201Created, a header field (header), and a message body. The URI1 generated in step 905 is carried in the header field, and the status code "201 Created" indicates that the NEF element successfully requests the policy authorization creation.
Optionally, the appessionid is carried in the message body.
905, after making a policy decision according to the application layer information, the network policy, and the user signing convention, the PCF network element sends a policy update notification Request (Npcf _ SMPolicy _ UpdateNotify Request) message to the SMF network element, where the Npcf _ SMPolicy _ UpdateNotify Request message carries the formulated policy.
specifically, as an example and not by way of limitation, the PCF network element sends an HTTP POST message to the SMF network element, where a message body of the HTTP POST message carries the formulated policy.
In addition, the HTTP POST message also carries a URL2 of the request, where the URL2 is an Update Notification (Update Notification) URL, the URL2 is provided by the SMF network element to the PCF network element when the SMF network element interacts with the PCF network element before, and the URL2 is used for policy Notification.
And 906, after the SMF network element saves the policy decision, sending a policy update notification Response (Npcf _ SMPolicy _ UpdateNotify Response) message to the PCF network element.
Specifically, by way of example and not limitation, the SMF network element sends an HTTP Response message to the PCF network element, where the HTTP Response message includes a Status Code (Status Code)200OK, and the Status Code "200 OK" indicates that the SMF network element successfully receives the Npcf _ SMPolicy _ UpdateNotify Request message sent by the PCF network element.
907, the NEF network element receives the trigger and needs to subscribe the event for the application session.
908, the NEF network element sends a policy authorization subscription Request (Npcf _ PolicyAuthorization _ subscription Request) message to the PCF network element, the Npcf _ PolicyAuthorization _ subscription Request message being used to Request a first event subscription from the PCF network element, the Npcf being a service-based interface exhibited by the PCF network element.
Specifically, as an example and not by way of limitation, the NEF network element sends HTTP PATCH a message to the PCF network element, where a message body of the HTTP PATCH message carries an appessentid and an Event identity Event Id1 corresponding to the first Event subscription, and the NEF network element assigns the appessentid carried in the HTTP Response message in step 904 as an association identity 1(Co-relation Id1) assigned to the first Event subscription by the PCF network element.
In addition, the HTTP PATCH message also carries the requested URL 2. For example, URL2 of the request: { apiRoot }/npcf-poliomyhoiation/v 1/app-sessions/appessionid/.
The PCF network element 909 sends an open event service subscription Request (Nsmf _ EventExposure _ Subscribe Request) message to the SMF network element, where the Nsmf _ EventExposure _ Subscribe Request message is used to Request a second event subscription to the SMF network element, and the Nsmf _ EventExposure _ Subscribe Request message carries Co-relation ID1 (e.g., appserviceid), and the Nsmf is a service-based interface exhibited by the SMF network element.
Specifically, as an example and not by way of limitation, the PCF network element sends an HTTP POST message to the SMF network element, where an Event identifier Event Id1 corresponding to the second Event subscription and a uniform resource locator neffevent Notification URL for receiving an Event report are carried in a message body of the HTTP POST message, and the Event Id1 may be a list of one or more events.
In addition, the HTTP POST message also carries any one of an identifier of the UE to which the second event subscription is directed, a group identifier of the UE, and indication information indicating that the second event subscription is directed to any UE.
In addition, the HTTP POST message also carries the URL3 of the request. For example, the URL3 for the request is: { apiRoot }/nsmf-event-exposure/v 1/subscriptions/.
it should be noted that the first event subscription requested by the Npcf _ PolicyAuthorization _ Subscribe Request message and the second event subscription requested by the Nsmf _ EventExposure _ Subscribe Request message are the same event subscriptions requested by the NEF network element, except that the first event subscription is subscribed to the PCF network element by the NEF network element through the Npcf _ PolicyAuthorization _ Subscribe message, and the second event subscription is subscribed to the SMF network element by the PCF network element through the Nsmf _ EventExposure _ Subscribe message. For example, when the PCF network element is unable to detect the first event subscription requested by the Npcf _ PolicyAuthorization _ subscription message, the PCF network element requests the SMF network element for the same event subscription (i.e., the second event subscription) as the first event subscription through the Nsmf _ EventExposure _ subscription message.
The SMF network element stores the subscription information and assigns a Co-relation ID2 for the second event subscription from the PCF network element 910.
Specifically, as an example and not by way of limitation, the SMF network element creates a resource for the second event subscription according to the information carried in the message body of the HTTP POST message, generates a sub-resource identifier 2 (e.g., a subscriptionid2), and constructs a uniform resource locator identifier 2 (e.g., a URI2) for the created resource, where the URI2 is generated by concatenating the sub-resource identifier 2subscriptionid2 with the URL3 of the request as a parent resource (parent resource).
For example, the URI2 is { apiRoot }/nsmf-event-issue/v 1/descriptions id 2.
The SMF network element assigns an association identification 2(Co-relation ID2) to the second event subscription. For example, the association identifier 2 is the child resource identifier 2 substinguistionid 2.
911, the SMF network element returns an event open service subscription Response (Nsmf _ EventExposure _ Subscribe Response) message to the PCF network element, where the Nsmf _ EventExposure _ Subscribe Response message carries the Co-relation ID 2.
Specifically, by way of example and not limitation, the SMF network element sends an HTTP Response message to the PCF network element, the HTTP Response message including a Status Code 201Created, a header field (header), and a message body. The URI2 generated in step 902 is carried in the header field, and the status code "201 Created" indicates that the second event subscription of the PCF network element is successful.
Optionally, the Co-relation ID2 carried in the message body is a subscriptionid 2.
912, the PCF network element saves the subscription information, updates the application session context and adds the Event identification Event Id 1.
Specifically, as an example and not by way of limitation, the first Event subscription is added to the resource created in step 903, i.e., the Event identification Event Id1 corresponding to the first Event subscription is added.
913, the PCF network element sends a policy authorization subscription Response (Npcf _ policy authorization _ subscription Response) message to the NEF network element, the Npcf _ policy authorization _ subscription Response message carrying the Co-relation ID 2.
Specifically, by way of example and not limitation, the PCF network element sends an HTTP Response message to the NEF network element, the HTTP Response message including a Status Code (Status Code)200OK, a header field (header), and a message body. Wherein, the header field carries the URI1 generated in step 903, the message body carries the subscriptionid2 (as an example of Co-relation ID2), and the status code "200 OK" indicates that the subscription of the first event of the NEF network element is successful.
In addition, as an example and not by way of limitation, in addition to carrying the subscriptionid2, the message body of the HTTP Response message sent by the PCF network element to the NEF network element may also carry an appessionid allocated by the PCF network element for the policy authorization creation request in step 703.
The SMF network element detects an Event that can be monitored by the SMF network element and matches the Event Id1 914.
915, the SMF network element sends an event open service notification Request (Nsmf _ EventExposure _ Notify Request) message to the NEF network element, where the Nsmf _ EventExposure _ Notify Request message carries event report information and Co-relation ID2 for the second event subscription of the PCF network element.
Specifically, by way of example and not limitation, the SMF network element sends an HTTP POST message to the NEF network element, where a message body of the HTTP POST message carries Event Id1 and subscriptionid2 detected by the SMF network element. Wherein the Nsmf is a service-based interface displayed by the SMF network element.
The NEF network element sends an event open service notification Response (Nsmf _ EventExposure _ Notify Response) message to the SMF network element 916.
Specifically, as an example and not by way of limitation, the NEF network element determines that the event report information carried in the Nsmf _ EventExposure _ notification Request message in step 915 is associated with the first event subscription according to the Co-relation Id2 carried in the Nsmf _ EventExposure _ notification Request message in step 915 and the Co-relation Id2 carried in the Npcf _ policy authorization _ notification Response message in step 913.
More specifically, when the Co-relation Id2 is SubscriptionId2, the NEF network element determines that the event report information carried in the HTTP POST message in step 915 is associated with the first event subscription according to the SubscriptionId2 carried in the HTTP POST message in step 915 and the SubscriptionId2 carried in the HTTP Response message in step 913.
And the NEF network element sends HTTP Response message to the SMF network element, wherein the HTTP Response message carries Status Code (Status Code)200OK, and the 200OK indicates successful reception of the HTTP POST message sent by the SMF network element.
As another optional implementation manner, in steps 911, 913, and 915, the Nsmf _ EventExposure _ Subscribe Response message sent by the SMF network element to the PCF network element, the Npcf _ PolicyAuthorization _ Subscribe Response message sent by the PCF network element to the NEF network element, and the Nsmf _ EventExposure _ Notify Request message sent by the SMF network element to the NEF network element carry, in addition to the Co-relation ID2, an SMF network element identifier (SMF ID), where the SMF ID indicates the SMF network element, and then the NEF network element determines that the event report information is associated with the first event subscription according to the Co-relation ID2, including:
The NEF network element determines that the event report information is associated with the first event subscription based on the Co-relation ID2 and the SMF ID.
Specifically, by way of example and not limitation, the Co-relation ID2 assigned by the SMF network element for the first event subscription may not be unique throughout the communication system.
At this time, the SMF network element adds an SMF ID capable of uniquely identifying the SMF network element to the Nsmf _ EventExposure _ Subscribe Response message and the Nsmf _ EventExposure _ Notify Request message, transmits the SMF ID to the NEF network element through the Nsmf _ EventExposure _ Notify Request message, transmits the SMF ID to the PCF network element through the Nsmf _ EventExposure _ Subscribe Response message, and transmits the SMF ID to the NEF network element through the Npcf _ policyautoxidation _ Subscribe Response message.
When the NEF network element receives the Npcf _ PolicyAuthorization _ Create Response message and the Nsmf _ EventExposure _ notification Request message, it can determine that the event report information is associated with the first event subscription according to the Co-relationship ID2 and the SMF ID in the Npcf _ PolicyAuthorization _ Create Response message, and according to the Co-relationship ID2 and the SMF ID in the Nsmf _ EventExposure _ notification Request message. Optionally, the SMF ID is an IP address of the SMF network element or an FQDN of the SMF network element.
Next, a method for subscribing to an event according to another embodiment of the present application will be described with reference to fig. 10 to 13.
Fig. 10 is a schematic flow chart of a method 1000 for subscribing to an event according to an embodiment of the present application.
It should be noted that, the first network functional network element described below may be the NEF network element 170 in fig. 1, the second network functional network element may be the UDM network element 190 in fig. 1, and the third network functional network element may be the AMF network element 150 in fig. 1; alternatively, the first network functional network element may be the NEF network element 170 in fig. 1, the second network functional network element may be the PCF network element 180 in fig. 1, and the third network functional network element may be the SMF network element 160 in fig. 1, which will not be described in detail later. The method 1000 includes at least the following steps.
1001, a first network function network element sends a first request message to a second network function network element, where the first request message is used to request a first event subscription from the second network function network element, and the first request message includes an event identifier.
Specifically, by way of example and not limitation, a first network function network element sends an Event open service subscription Request (Nnf2_ EventExposure _ Subscribe Request) message (e.g., a first Request message) to a second network function network element, Nnf2 a service-based interface exposed for the second network function network element, the first Request message including an Event Id1 (e.g., an Event identifier), and further including any one of an identity of a UE for which the first Event subscription is intended, a group identity of the UE, and indication information indicating that the first Event subscription is intended for any UE, and a uniform resource locator Nf1Event Notification URL of a reception Event report, the first Request message for requesting an Event subscription (e.g., a first Event subscription) from the second network function network element.
In addition, the first request message also includes the requested URL 1. For example, the URL1 of the request is that the URL is: { apiRoot }/nnf2-event-exposure/v 1/subscriptions/.
And 1002, the second network function network element receives a first request message sent by the first network function network element, where the first request message is used to request the second network function network element for a first event subscription, and the first request message includes an event identifier.
Specifically, by way of example and not limitation, the second network function network element receives the first request message sent by the first network function network element, creates a resource for the first event subscription according to the information in the first request message, generates a child resource identifier 1 (e.g., a subscriptionid1), and constructs a uniform resource locator identifier 1 (e.g., a URI1) for the created resource, where the URI1 is generated by concatenating the child resource identifier 1 subferrionid 1 with the URL1 of the request as a parent resource (parent resource).
For example, the URI1 is { apiRoot }/nnf 2-event-issue/v 1/descriptors id 1.
the second network functional network element assigns an association identification 1(Co-relation ID1) (e.g., a fifth identification) to the first event subscription.
Optionally, the fifth identifier is an identifier of a resource created by the second network function network element for the first event subscription.
For example, the fifth identification may be a sub-resource identification 1 sub-scriptionid 1 of the resource created by the second network function network element for the first event subscription.
In addition, the second network function network element may further create a sub-resource of the Event description in the resource created by the first Event Subscription, where the corresponding sub-resource URI1a is { apiRoot }/npcf-poliomyhoza/v 1/app-sessions/appessionid/events-description.
The second network function network element may assign this URI1a as Co-relation ID1 to the first event subscription, i.e. the fifth identity may also be URI1 a. And the second network function network element sends the fifth identifier to the first network function network element. Please refer to step 1005 for detailed description; and the second network function network element sends the fifth identifier to a third network function network element. Please refer to step 1003 for a detailed description.
1003, the second network function network element sends a second request message to the third network function network element, where the second request message is used to request, from the third network function network element, the first network function network element for notification of the event corresponding to the event identifier, the second request message includes the event identifier and a fifth identifier, and the fifth identifier is an identifier that is allocated to the first event subscription by the second network function network element.
Specifically, as an example and not by way of limitation, the second network functional network element determines, according to the Event Id1 carried in the received first Request message, that the first Event subscription requested by the first network functional network element cannot be detected, at this time, the second network functional network element sends an Event open service subscription Request (Nnf3_ Event expose _ Subscribe Request) message (e.g., a second Request message) to a third network functional network element, Nnf3 is a service-based interface presented by the third network functional network element, and the second Request message is used for requesting, by the first network functional network element, a notification of an Event corresponding to the Event Id1 from the third network functional network element. That is, the second network function network element requests the third network function network element for notification of the Event corresponding to the Event Id1 instead of the first network function network element, and the second request message includes the Event identification Event Id1 and the fifth identification.
By way of example and not limitation, the second request message may include a policy rule including the Event identification Event Id1 and the fifth identification.
In addition, the second request message further includes a uniform resource locator Nf2Event Notification URL for receiving an Event report and any one of an identifier of a UE to which the first Event subscription is directed, a group identifier of the UE, and indication information indicating that the first Event subscription is directed to any UE.
In addition, the second request message also includes the requested URL 2. For example, the URL2 for the request is: { apiRoot }/nnf3-event-exposure/v 1/subscriptions/.
1004, the third network function network element receives a second request message sent by the second network function network element, where the second request message is used for requesting, by the first network function network element, the third network function network element for notification of an event corresponding to the event identifier, the second request message includes the event identifier and a fifth identifier, the fifth identifier is an identifier allocated by the second network function network element for subscription of the first event, and the subscription of the first event is an event subscription requested by the first network function network element from the second network function network element.
Specifically, by way of example and not limitation, the third network function network element receives the second request message sent by the second network function network element, creates a resource for the Event corresponding to the Event Id1 according to the information in the second request message, generates a sub-resource identifier 2 (e.g., a subscribentid 2), and constructs a uniform resource locator identifier 2 (e.g., a URI2) for the created resource, where the URI2 is generated by concatenating the URL2 of the request as a parent resource (parent resource) with the sub-resource identifier subscribentied 2.
For example, the URI2 is { apiRoot }/nnf 3-event-issue/v 1/descriptors id 2.
The third network functional network element assigns an association identification 2(Co-relation ID2) to the second event subscription. For example, the association identifier 2 identifies the subscribentid 2 for the child resource.
And 1005, the second network function network element sending a first reply message to the first network function network element, the first reply message including the fifth identifier.
Specifically, by way of example and not limitation, the second network function network element sends an event open service response (Nnf2_ EventExposure _ subscribe) message (e.g., a first response message) to the first network function network element after assigning the fifth identity for the first event subscription, the Nnf2 being a service-based interface exposed by the second network function network element, the second response message including the fifth identity.
And 1006, the first network function network element receives an event notification sent by the third network function network element, where the event notification includes the event identifier and the fifth identifier.
Wherein the event notification includes event report information. The event notification may specifically be an event notification message. The event notification message includes event report information, and the event report information includes an event identifier and the fifth identifier.
Specifically, the first network functional network element receives the first response message sent by the second network functional network element, and acquires the fifth identifier according to the first response message.
1007, the third network function network element sends an event notification to the first network function network element according to the second request message, where the event notification includes the event identifier and the fifth identifier.
Specifically, as an example and not by way of limitation, the third network function network element detects an Event matching the Event identifier Event Id1 carried in the second Event subscription, and sends an Event openservice notification Request (Nnf3_ evendexopossures _ Notify Request) message to the first network function network element, where the Nnf3 is a service-based interface exposed by the third network function network element, the Event openservice notification Request message includes an Event notification for the second Event subscription, and the Event notification includes the Event identifier Event Id1 and the fifth identifier.
And 1008, the first network function network element receives an event notification sent by the third network function network element, where the event notification includes the event identifier and the fifth identifier.
1009, the first network functional network element determines, according to the fifth identifier, that the event notification is associated with the first event subscription.
Specifically, by way of example and not limitation, the first network function network element receives the event open service notification request message sent by the third network function network element, and receives the first reply message sent by the second network function network element, and determines that the event notification is associated with the first event subscription according to a fifth identifier (for example, the fifth identifier may be URI1 or URI1a) carried in the first reply message and the fifth identifier carried in the event notification.
Thus, by having an intermediate network element (e.g., the second network function network element) generate the association identification in accordance with the event subscription requested by the network element requesting the event subscription (e.g., the first network function network element), and sends the associated identifier (e.g., a fifth identifier) to the first network function network element and the network element sending the event report (e.g., a third network function network element), and when the third network functional network element receives an event subscription that the second network functional network element requests from the third network functional network element for the first network functional network element, the third network function network element sends the first identifier carried in the event notification to the first network function network element, enabling the first network function network element to determine that the event subscription requested from the second network function network element is associated with the event notification received from the third network function network element according to the association identifier.
it should be noted that, in this embodiment of the present application, the fifth identifier may be globally unique, and at this time, the first network function network element may determine, according to the fifth identifier only, that the event subscription requested from the second network function network element is associated with the event notification received from the third network function network element.
When the fifth identifier is not globally unique, in steps 1003, 1005 and 1007, the second request message sent by the second network functional network element to a third network functional network element, the event notification sent by the third network functional network element to the first network functional network element, and the first reply message sent by the second network functional network element to the first network functional network element, in addition to carrying the fifth identifier, also include an identifier for indicating the second network functional network element, the identity indicating the second network function network element may be an identity (FQDN) or an address (Ipv4 or Ipv6 address) of the second network function network element, and the first network function network element determines that the event notification is associated with the first event subscription according to the fifth identifier and the identifier for indicating the second network function network element.
in particular, by way of example and not limitation, the fifth identification assigned by the second network function network element to the first event subscription is not globally unique.
when the fifth identifier is globally non-unique, the second network function network element is capable of adding an identifier uniquely identifying the second network function network element (i.e., an identifier indicating the second network function network element) to the first reply message and the second request message, sending the identifier indicating the second network function network element to the first network function network element through the first reply message, sending the identifier indicating the second network function network element to the third network function network element through the second request message, and sending the identifier indicating the second network function network element to the first network function network element through an event notification by the third network function network element.
when the first network function network element receives the first reply message and the event notification, it is able to determine that the event notification is associated with the first event subscription according to the fifth identifier in the first reply message and the identifier indicating the second network function network element, and according to the fifth identifier in the event notification and the identifier indicating the second network function network element.
optionally, the identifier indicating the second network function network element may also be an IP address of the second network function network element or an FQDN of the second network function network element.
thus, by having the second network function network element provide an identification uniquely identifying the second network function (i.e. an identification indicating the second network function network element) and the fifth identification to the first network function network element and the third network function network element when the fifth identification is not unique, and when the third network functional network element receives an event subscription that the second network functional network element requests from the third network functional network element for the first network functional network element, the third network function network element sends the fifth identifier and the identifier indicating the second network function network element to the first network function network element in an event notification, enabling the first network function network element to determine that the event subscription requested from the second network function network element is associated with the event notification received from the third network function network element according to the fifth identifier and the identifier indicating the second network function network element.
Fig. 11 is a schematic flow chart diagram of a method 2000 for subscribing to an event according to another embodiment of the present application. The method 2000 includes at least the following steps.
2001, a first network function network element sends a first request message to a second network function network element, where the first request message is used to request the second network function network element for a first event subscription, and the first request message carries an event identifier.
Specifically, by way of example and not limitation, a first network function network element sends an Event open service subscription Request (Nnf2_ EventExposure _ Subscribe Request) message (e.g., a first Request message) to a second network function network element, Nnf2 a service-based interface exposed for the second network function network element, the first Request message including an Event Id1 (e.g., an Event identifier), and further including any one of an identity of a UE for which the first Event subscription is intended, a group identity of the UE, and indication information indicating that the first Event subscription is intended for any UE, and a uniform resource locator Nf1Event Notification URL of a reception Event report, the first Request message for requesting an Event subscription (e.g., a first Event subscription) from the second network function network element.
In addition, the first request message also includes the requested URL 1. For example, the URL1 of the request is that the URL is: { apiRoot }/nnf2-event-exposure/v 1/subscriptions/.
2002, the second network function network element receives a first request message sent by the first network function network element, the first request message being for requesting a first event subscription from the second network function network element, the first request message including an event identification.
Specifically, by way of example and not limitation, the second network function network element receives the first request message sent by the first network function network element, subscribes to the created resource for the first event according to the information in the first request message, generates a child resource identifier 1 (e.g., subscriptionid1), and constructs a uniform resource locator identifier 1 (e.g., URI1) for the created resource, where the URI1 is generated by concatenating the child resource identifier 1 subftionand 1 with the URL1 of the request as a parent resource (parent resource).
For example, the URI1 is { apiRoot }/nnf 2-event-issue/v 1/descriptors id 1.
The second network function network element assigns an intermediate identifier (e.g., a fifth identifier) to the first event subscription and sends the fifth identifier to the first network function network element. See step 2005 for a detailed description.
For example, the fifth identification may be a URI 1.
in addition, the second network function network element may further create a sub-resource of the Event description in the resource created for the first Event Subscription, where the corresponding sub-resource URI1a is { apiRoot }/npcf-poliyanthonization/v 1/app-sessions/appessionid/events-description.
the second network function element may assign association identifier 1(Co-relation ID1) (e.g., a sixth identifier) to the first event subscription, and send the association identifier 1 to the third network function element, as described in step 2003.
Optionally, the sixth identifier is an identifier of a resource created by the second network function network element for the first event subscription.
For example, the sixth identifier may be URI1a
2003, the second network function network element sends a second request message to the third network function network element, where the second request message is used to request, from the third network function network element, the first network function network element for notification of the event corresponding to the event identifier, the second request message includes the event identifier and the sixth identifier, and the sixth identifier is an identifier of the resource that is created for the first event subscription by the second network function network element.
Specifically, as an example and not by way of limitation, the second network functional network element determines, according to the Event Id1 carried in the received first Request message, that the first Event subscription requested by the first network functional network element cannot be detected, at this time, the second network functional network element sends an Event open service subscription Request (Nnf3_ Event expose _ Subscribe Request) message (e.g., a second Request message) to a third network functional network element, Nnf3 is a service-based interface presented by the third network functional network element, and the second Request message is used for requesting, by the first network functional network element, a notification of an Event corresponding to the Event Id1 from the third network functional network element. That is, the second network function network element requests the third network function network element for notification of the Event corresponding to the Event Id1, instead of the first network function network element. Wherein, the Event identifier Event Id1 and the sixth identifier are included in the second request message.
By way of example and not limitation, the second request message may include a policy rule including the Event identification Event Id1 and the sixth identification.
2004, the third network function network element receives a second request message sent by the second network function network element, where the second request message is used to request, for the first network function network element, the third network function network element for notification of an event corresponding to the event identifier, the second request message includes the event identifier and the sixth identifier, and the first event subscription is an event subscription requested by the first network function network element from the second network function network element.
Specifically, by way of example and not limitation, the third network function network element receives the second request message sent by the second network function network element, creates a resource for the Event corresponding to the Event Id1 according to the information in the second request message, generates a sub-resource identifier 2 (e.g., a subscribentid 2), and constructs a uniform resource locator identifier 2 (e.g., a URI2) for the created resource, where the URI2 is generated by concatenating the URL2 of the request as a parent resource (parent resource) with the sub-resource identifier subscribentied 2.
For example, the URI2 is { apiRoot }/nnf 3-event-issue/v 1/descriptors id 2.
The third network functional network element assigns an association identification 2(Co-relation ID2) to the second event subscription. For example, the association identifier 2 identifies the subscribentid 2 for the child resource.
2005, the second network functional network element sends a first reply message to the first network functional network element, the first reply message including the fifth identity.
Specifically, by way of example and not limitation, the second network function network element sends an event open service response (Nnf2_ EventExposure _ subscribe) message (e.g., a first response message) to the first network function network element after assigning the fifth identity for the first event subscription, the Nnf2 being a service-based interface exposed by the second network function network element, the second response message including the fifth identity.
2006, the first network function network element receives the first reply message sent by the second network function network element.
Specifically, the first network functional network element receives the first response message sent by the second network functional network element, and acquires the fifth identifier according to the first response message.
2007, the first network function network element obtains the sixth identifier according to the fifth identifier.
In particular, by way of example and not limitation, the first network function network element may obtain the sixth identity (e.g., URI1a) from the fifth identity (e.g., URI 1).
By way of example and not limitation, the first network function network element may generate the sixth identity (e.g., URI1a) from the fifth identity (e.g., URI 1). For example, the first network function network element adds/events-descriptions on the basis of the URI 1.
The URI1a generated by the first network function network element is { apiRoot }/npcf-poliomyhosition/v 1/app-sessions/appessionid/events-description.
2008, the third network function network element sends an event notification to the first network function network element according to the second request message, where the event notification includes the event identifier and the sixth identifier.
Specifically, as an example and not by way of limitation, the third network function network element detects an Event matching the Event identifier Event Id1 carried in the second Event subscription, and sends an Event openservice notification Request (Nnf3_ evendexopoursure _ Notify Request) message to the first network function network element, where the Nnf3 is a service-based interface exposed by the third network function network element, the Event openservice notification Request message includes an Event notification for the second Event subscription, and the Event notification includes the Event identifier Event Id1 and the sixth identifier.
2009, the first network function network element receives the event notification sent by the third network function network element.
2010, the first network function network element determines, according to the sixth identifier, that the event notification is associated with the first event subscription.
Specifically, by way of example and not limitation, the first network function network element receives the event open service notification request message sent by the third network function network element, and receives the first reply message sent by the second network function network element, and determines that the event notification is associated with the first event subscription according to a sixth identifier (for example, the sixth identifier may be URI1a) carried in the first reply message and the sixth identifier carried in the event notification.
Wherein the event notification includes event report information. The event notification may specifically be an event notification message. The event notification message includes event report information, and the event report information includes an event identifier and the sixth identifier.
thus, by making an intermediate network element (e.g., a second network function network element) subscribe to an event requested by a network element (e.g., a first network function network element) requesting an event subscription, generating an intermediate identifier (e.g., a fifth identifier) and an associated identifier (e.g., a sixth identifier), and sending the intermediate identifier to the first network function network element, sending the associated identifier to a network element (e.g., a third network function network element) that is reporting the event, and making the third network function network element carry the sixth identifier in an event notification to the first network function network element when the third network function network element receives the event subscription that the second network function network element requests from the third network function network element, the first network function network element generates the sixth identifier according to the fifth identifier, so that the first network function network element can transmit the sixth identifier according to the sixth identifier, it is determined that the event subscription requested from the second network functional network element is associated with an event notification received from a third network functional network element.
it should be noted that, in this embodiment of the present application, the fifth identifier or the sixth identifier may be globally unique, and at this time, the first network function network element may obtain the sixth identifier according to the fifth identifier, and determine that the event subscription requested to the second network function network element is associated with the event notification received from the third network function network element only according to the sixth identifier.
when the fifth identity or the sixth identity is not globally unique, in steps 2003, 2005 and 2008, the second request message sent by the second network functional network element to the third network functional network element and the event notification sent by the third network functional network element to the first network functional network element carry, in addition to the sixth identity, an identity indicating the second network functional network element, the first reply message sent by the second network functional network element to the first network functional network element also carries, in addition to the fifth identity, an identity indicating the second network functional network element, which may be an identity (FQDN) or an address (Ipv4 or Ipv 6) of the second network functional network element, wherein the fifth identity, the sixth identity are respectively associated with the identity indicating the second network functional network element and the first event subscription, and the first network function network element determines that the event notification is associated with the first event subscription according to the sixth identifier and the identifier indicating the second network function network element.
In particular, by way of example and not limitation, the fifth identity or the sixth identity assigned by the second network functional network element to the first event subscription may not be unique throughout the communication system.
When the fifth identity or the sixth identity is not globally unique, the second network functional network element is capable of adding an identity uniquely identifying the second network functional network element (i.e. an identity indicating a second network functional network element) to the first reply message and the second request message, sending the identity indicating the second network functional network element to the first network functional network element via the first reply message, and sending the identity indicating the second network functional network element to the third network functional network element via the second request message, and sending the identity indicating the second network functional network element to the first network functional network element via an event notification by the third network functional network element.
When the first network function network element receives the first reply message and the event notification, the sixth identifier can be generated according to the fifth identifier in the first reply message, and the event notification is determined to be associated with the first event subscription according to the sixth identifier and the identifier indicating the second network function network element, and according to the sixth identifier in the event notification and the identifier indicating the second network function network element.
Optionally, the identifier indicating the second network function network element may also be an IP address of the second network function network element or an FQDN of the second network function network element.
Therefore, when the fifth identifier or the sixth identifier is not unique, by enabling the second network function network element to provide the identifier uniquely identifying the second network function (i.e. the identifier indicating the second network function network element) and the fifth identifier to the first network function network element, and to provide the identifier indicating the second network function network element and the sixth identifier to the third network function network element, and when the third network function network element receives the event subscription that is requested by the first network function network element from the third network function network element for the second network function network element, enabling the third network function network element to carry the sixth identifier and the identifier indicating the second network function network element in an event notification to send to the first network function network element, the first network function network element can generate the sixth identifier according to the fifth identifier, so that the first network function network element can generate the sixth identifier according to the sixth identifier and the identifier indicating the second network function network element, it is determined that the event subscription requested from the fifth identified network element of the second network function is associated with the event notification received from the third network function network element.
For better understanding of the method for subscribing to the event provided by the present application, taking the first network functional network element as the NEF network element 170 in fig. 1, the second network functional network element as the UDM network element 190 in fig. 1, and the third network functional network element as the AMF network element 150 in fig. 1 as an example, the method 1000 for subscribing to the event provided by the present application is further described in detail with reference to the method 3000 shown in fig. 12. The method comprises at least the following steps.
3001, the NEF network element receives a trigger, possibly from other NF network elements (e.g. AF network elements) or internally, to request policy authorization from the PCF network element. The trigger from the AF network element may be policy authorization from the AF network element to the NEF network element.
3002, the NEF network element sends a policy authorization creation Request (Npcf _ PolicyAuthorization _ Create Request) message to the PCF network element, the Npcf _ PolicyAuthorization _ Create Request message including application layer information, the application layer information being used for requesting policy authorization. Wherein, the Npcf is a service-based interface displayed by the PCF network element.
Specifically, by way of example and not limitation, the NEF network element sends an HTTP POST message to the PCF network element, including application layer information in the message body of the HTTP POST message.
In addition, the HTTP POST message also includes the requested URL 1. For example, the URL1 for the request is: { apiRoot }/npcf-poliomyhoiation/v 1/app-sessions/.
3003 the PCF network element saves the information and creates an application session context.
Specifically, by way of example and not limitation, the PCF network element creates a resource for the application session according to the information included in the message body of the HTTP POST message in step 3002, generates a sub-resource identifier 1 appessionid, and constructs a URI1 for this created resource. The URI1 is generated using the URL1 of the request as the parent resource (parent resource) and concatenating the child resource identification 1 appessionid.
For example, the URI1 is { apiRoot }/npcf-polirecognition/v 1/app-sessions/appessionid/.
3004, the PCF network element sends a policy authorization creation Response (Npcf _ PolicyAuthorization _ Create Response) message to the NEF network element.
Specifically, by way of example and not limitation, the PCF network element sends an HTTP Response message to the NEF network element, the HTTP Response message including a Status Code 201Created, a header field (header), and a message body. Wherein, the header field includes the URI1 generated in step 3003, and the status code "201 Created" indicates that the NEF network element successfully requests the policy authorization creation.
Optionally, the appessionid is included in the message body.
3005, after making policy decision according to the application layer information, the network policy and the user signing convention, the PCF network element sends a Session Management (SM) policy update notification Request (Npcf _ SMPolicy _ UpdateNotify Request) message to the SMF network element, where the Npcf _ SMPolicy _ UpdateNotify Request message includes a formulated policy, including a PCC rule.
Specifically, by way of example and not limitation, the PCF network element sends an HTTP POST message to the SMF network element, where a message body of the HTTP POST message includes the formulated policy.
In addition, the HTTP POST message also includes a URL2 of the request, where the URL2 is an Update Notification (Update Notification) URL, the URL2 is provided to the PCF network element by the SMF network element when the SMF network element previously interacted with the PCF network element, and the URL2 is used for policy Notification.
3006, after the SMF network element saves the policy decision, it sends a session management policy update notification Response (Npcf _ SMPolicy _ UpdateNotify Response) message to the PCF network element.
Specifically, by way of example and not limitation, the SMF network element sends an HTTP Response message to the PCF network element, where the HTTP Response message includes a Status Code (Status Code)200OK, and the Status Code "200 OK" indicates that the SMF network element successfully receives the Npcf _ SMPolicy _ UpdateNotify Request message sent by the PCF network element.
3007, the NEF network element receives a trigger that requires event subscription for the application session.
3008, the NEF network element sends a policy authorization subscription Request (Npcf _ PolicyAuthorization _ Subscribe Request) message to the PCF network element, the Npcf _ PolicyAuthorization _ Subscribe message being used to Request a first event subscription from the PCF network element, the Npcf being a service-based interface exhibited by the PCF network element.
Specifically, by way of example and not limitation, the NEF network element sends HTTP PATCH or an HTTP PUT message to the PCF network element, where a message body of the HTTP PATCH or the HTTP PUT message includes an Event identifier Event Id1 corresponding to the first Event subscription and a uniform resource locator neffevent Notification URL of the NEF receiving the Event Notification.
In addition, the HTTP PATCH message includes the requested URL 2. For example, the URL2 for the request is: { apiRoot }/npcf-poliomyhoiation/v 1/app-sessions/appessionid/.
3009, the PCF network element saves the subscription information, updates the application session context and adds the Event identification Event Id 1.
Specifically, by way of example and not limitation, a sub-resource of Event description is created in the resources created in step 3003, whose corresponding sub-resource URI1a is
{apiRoot}/npcf-policyauthorization/v1/app-sessions/appsessionid/events-subscription。
3010, the PCF network element sends a policy authorization subscription Response (Npcf _ PolicyAuthorization _ Subscribe Response) message to the NEF network element.
Specifically, by way of example and not limitation, the PCF network element sends an HTTP Response message to the NEF network element, the HTTP Response message including a Status Code (Status Code)200OK, the Status Code "200 OK" indicating that the NEF network element successfully completed the first event subscription. URI1a is included in the Location header of the return message to send to the NEF.
NEF may subscribe URI1a as an association identifier 1(Co-relation ID1) for the first event.
The PCF may also include the URI1 in the Location header of the return message for sending to the NEF.
NEF can subscribe URI1 as the association identifier 1(Co-relation ID1) for the first event.
3011, the PCF updates the previous PCC rule, and includes Co-relation ID1 (for example, URI1a), Event ID1, and neffevent Notification URL (which is equivalent to including the first subscription information from the NEF in the PCC rule), and the PCF network element sends an Npcf _ SMPolicy _ update Notification Request message to the SMF, where the Npcf _ SMPolicy _ update Notification Request message is used to send the updated PCC rule to the SMF network element. Specifically, by way of example and not limitation, the PCF network element sends an HTTP POST message to the SMF network element, where the message body of the HTTP POST message includes URI1a, an Event identity Event Id1 and a neffevent Notification URL, and the Event Id1 may be a list of one or more events. The PCF includes information about the event subscription in the PCC rule, which corresponds to an implicit subscription to the related event.
3012, install or update the PCC rule in the SMF, and perform Event monitoring according to the Event Id1 included in the PCC rule.
3013, the SMF network element returns an Npcf _ SMPolicy _ UpdateNotify Response message to the PCF network element, the message including Co-relation ID 2.
3014, the SMF network element detects an Event that can be monitored by the SMF network element and matches the Event Id 1.
3015, the SMF network element sends an Event open service notification Request (Nsmf _ EventExposure _ Notify Request) message to the NEF network element, where the Nsmf _ EventExposure _ Notify Request message includes Event Id1 corresponding to the Event report information and Co-relation Id1 (e.g., URI1a) from the NEF included in the detected PCC rule.
Specifically, by way of example and not limitation, the SMF network element sends an HTTP POST message to the NEF network element, the message body of the HTTP POST message including the SMF network element detected Event Id1 and URI1 a.
3016, the NEF network element sends an event open service notification Response (Nsmf _ EventExposure _ Notify Response) message to the SMF network element.
Specifically, by way of example and not limitation, the NEF network element determines that the event report information included in the Nsmf _ EventExposure _ notification Request message in step 3015 is associated with the first event subscription according to the Co-relationship ID1 included in the Nsmf _ EventExposure _ notification Request message in step 3015 and the Co-relationship ID1 (e.g., URI1 or URI1a) included in the Npcf _ policy authorization _ Create Response message in step 3010.
More specifically, when the Co-relation ID1 is URI1 or URI1a, the NEF network element determines that the event report information included in the Nsmf _ EventExposure _ Notify Request message in step 3015 is associated with the first event subscription according to URI1 or URI1a included in the HTTP POST message in step 3015 and URI1 or URI1a included in the HTTP Response message in step 3010. And the NEF network element sends an HTTP Response message to the SMF network element, where the HTTPResponse message includes a Status Code (Status Code)200OK, and the "200 OK" indicates that the Nsmf _ EventExposure _ Notify Request message returned by the SMF network element is successfully received.
Taking the first network functional network element as the NEF network element 170 in fig. 1, the second network functional network element as the PCF network element 180 in fig. 1, and the third network functional network element may be the SMF network element 160 in fig. 1 as an example, the method 2000 for subscribing to an event provided by the present application is further described in detail with reference to the method 4000 shown in fig. 13. The method comprises at least the following steps.
4001, the NEF network element receives a trigger, which may be from another NF network element (e.g., an AF network element) or internal, to decide to request policy authorization and event subscription from the PCF network element. The trigger from the AF network element may be policy authorization and event subscription performed by the AF network element to the NEF network element.
4002, the NEF network element sends a policy authorization creation Request (Npcf _ PolicyAuthorization _ Create Request) message to the PCF network element, the Npcf _ PolicyAuthorization _ Create Request message including application layer information, the application layer information being used for requesting policy authorization and event subscription. Wherein, the Npcf is a service-based interface displayed by the PCF network element.
specifically, by way of example and not limitation, the NEF network element sends an HTTP POST message to the PCF network element, where the message body of the HTTP POST message includes application layer information and Event subscription information, and the Event subscription information includes an Event identifier Event Id1 and a URI, such as a neffevent Notification URI, at which the NEF receives an Event Notification.
In addition, the HTTP POST message also includes the requested URL 1. For example, the URL1 for the request is: { apiRoot }/npcf-poliomyhoiation/v 1/app-sessions/.
4003, the PCF network element saves the information and creates an application session context and an event subscription.
Specifically, by way of example and not limitation, the PCF network element creates a resource for the application session according to the information included in the message body of the HTTP POST message in step 4002, generates a sub-resource identifier 1 appessionid, and constructs a URI1 for this created resource. The URI1 is generated using the URL1 of the request as the parent resource (parent resource) and concatenating the child resource identification 1 appessionid.
For example, the URI1 is { apiRoot }/npcf-polirecognition/v 1/app-sessions/appessionid/.
PCF further creates sub-resource of Event Subscription according to the Event Subscription related information in the message, wherein the corresponding sub-resource URI1a is
{apiRoot}/npcf-policyauthorization/v1/app-sessions/appsessionid/events-subscription
4004, the PCF network element sends a policy authorization creation Response (Npcf _ PolicyAuthorization _ Create Response) message to the NEF network element.
specifically, by way of example and not limitation, the PCF network element sends an HTTP Response message to the NEF network element, the HTTP Response message including a Status Code 201Created, a header field (header), and a message body. Wherein, the header field includes the URI1 generated in step 4004, and the status code "201 Created" indicates that the NEF network element successfully requests the policy authorization creation. NEF can generate URI1a from URI1, i.e. NEF generates URI1a after adding/events-descriptions on the basis of URI 1.
4005, after performing policy decision according to the application layer information, the network policy, and the user signing convention, the PCF network element sends a Session Management (SM) policy update notification Request (Npcf _ SMPolicy _ UpdateNotify Request) message to the SMF network element, where the Npcf _ SMPolicy _ UpdateNotify Request message includes a formulated policy, including a PCC rule. In addition, the PCF directly includes the information related to the Event subscription in the formulated PCC rule, including URI1 or URI1a, Event Id1 and neffevent Notification URL in the PCC rule.
Specifically, by way of example and not limitation, the PCF network element sends an HTTP POST message to the SMF network element, where a message body of the HTTP POST message includes the formulated policy.
In addition, the HTTP POST message also includes a URL2 of the request, where the URL2 is an Update Notification (Update Notification) URL, the URL2 is provided to the PCF network element by the SMF network element when the SMF network element previously interacted with the PCF network element, and the URL2 is used for policy Notification.
4006, after the SMF network element saves the policy decision, sending a session management policy update notification Response (Npcf _ SMPolicy _ UpdateNotify Response) message to the PCF network element. And the SMF detects the event according to the event subscription information included by the PCC rule.
specifically, by way of example and not limitation, the SMF network element sends an HTTP Response message to the PCF network element, where the HTTP Response message includes a Status Code (Status Code)200OK, and the Status Code "200 OK" indicates that the SMF network element successfully receives the Npcf _ SMPolicy _ UpdateNotify Request message sent by the PCF network element.
4007, the SMF network element detects an Event that can be monitored by the SMF network element and that matches the Event Id 1.
4008, the SMF network element sends an Event open service notification Request (Nsmf _ EventExposure _ Notify Request) message to the NEF network element, where the Nsmf _ EventExposure _ Notify Request message includes Event report information corresponding to the Event Id1 from the NEF included in the detected PCC rule and URI1 a.
Specifically, by way of example and not limitation, the SMF network element sends an HTTP POST message to the NEF network element, the message body of the HTTP POST message including the SMF network element detected Event Id1 and URI1 a.
4009, the NEF network element sends an event open service notification Response (Nsmf _ EventExposure _ Notify Response) message to the SMF network element.
Specifically, as an example and not by way of limitation, the NEF network element determines that the event report information included in the Nsmf _ EventExposure _ Notify Request message in step 4008 is associated with the first event subscription according to URI1a included in the Nsmf _ EventExposure _ Notify Request message in step 4008 and URI1a generated by NEF according to URI1 included in the Npcf _ policyautomation _ Create Response message in step 4004.
The method for subscribing to the event provided by the embodiment of the present application is described above with reference to fig. 4 to 13, and the network functional network element provided by the embodiment of the present application is described below with reference to fig. 14 to 19.
Fig. 14 is a schematic block diagram of a first network function network element 1000 according to an embodiment of the present application, where the first network function network element includes a sending module 1001, a receiving module 1002, and a processing module 1003.
A sending module 1001, configured to send a first request message to a second network function network element, where the first request message is used to request the second network function network element for a first event subscription, and the first request message carries an event identifier.
A receiving module 1002, configured to receive a first response message sent by the second network function network element, where the first response message carries a first identifier, and the first identifier is an identifier that is allocated to the first event subscription by the second network function network element.
The receiving module 1002 is further configured to receive event report information sent by a third network function network element, where the event report information carries the event identifier and the first identifier.
The processing module 1003 is configured to determine, according to the first identifier, that the event report information is associated with the first event subscription.
Optionally, the first reply message and the event report information further carry a second identifier, where the second identifier is used to indicate the second network function network element, and the first identifier and the second identifier are used to associate with a first event subscription;
The processing module 1003 is further configured to determine that the event reporting information is associated with the first event subscription according to the first identifier and the second identifier.
As another embodiment, the sending module 1001, the receiving module 1002 and the processing module 1003 in the first network functional network element 1000 are configured to execute the following steps:
A sending module 1001, configured to send a first request message to a second network function network element, where the first request message is used to request a first event subscription to the second network function network element, and the first request message carries an event identifier;
a receiving module 1002, configured to receive a first response message sent by the second network functional network element, where the first response message carries a third identifier, where the third identifier is an identifier allocated by the third network functional network element for a second event subscription, and the second event subscription is an event subscription requested by the second network functional network element to the third network functional network element;
the receiving module 1002 is further configured to receive event report information sent by a third network function network element, where the event report information carries the event identifier and the third identifier;
The processing module 1003 is configured to determine, according to the third identifier, that the event report information is associated with the first event subscription.
Optionally, the first reply message and the event report information further carry a fourth identifier, where the fourth identifier is used to indicate the third network function network element, and the third identifier and the fourth identifier are used to associate with the first event subscription;
The processing module 1003 is further configured to determine that the event reporting information is associated with the first event subscription according to the third identifier and the fourth identifier.
As another embodiment, the sending module 1001, the receiving module 1002 and the processing module 1003 in the first network functional network element 1000 are configured to execute the following steps:
A sending module 1001, configured to send a first request message to a second network function network element, where the first request message is used to request a first event subscription from the second network function network element, and the first request message includes an event identifier;
A receiving module 1002, configured to receive a first response message sent by the second network function network element, where the first response message includes a fifth identifier, and the fifth identifier is an identifier that is allocated to the first event subscription by the second network function network element;
The receiving module 1002 is further configured to receive an event notification sent by a third network function network element, where the event notification includes the event identifier and the fifth identifier;
The processing module 1003 is configured to determine, according to the fifth identifier, that the event report information is associated with the first event subscription.
Optionally, the fifth identifier is an identifier of a resource created by the second network function network element for the first event subscription.
Optionally, the second request message further includes a policy rule, where the policy rule includes the event identifier and the fifth identifier.
As another embodiment, the sending module 1001, the receiving module 1002 and the processing module 1003 in the first network functional network element 1000 are configured to execute the following steps:
A sending module 1001, configured to send a first request message to a second network function network element, where the first request message is used to request a first event subscription from the second network function network element, and the first request message includes an event identifier;
A receiving module 1002, configured to receive a first response message sent by the second network functional network element, where the first response message carries a fifth identifier;
A processing module 1003, configured to obtain a sixth identifier according to the fifth identifier;
The receiving module 1002 is further configured to receive an event notification sent by a third network function network element, where the event notification includes the event identifier and the sixth identifier;
The processing module 1003 is further configured to determine, according to the sixth identifier, that the event notification is associated with the first event subscription.
Optionally, the sixth identifier is an identifier of a resource created by the second network function network element for the first event subscription.
Optionally, the second request message further includes a policy rule, where the policy rule includes the event identifier and the sixth identifier.
It should be understood that the processing module 1003 in the embodiment of the present invention may be implemented by a processor or a processor-related circuit component, and the transmitting module 1001 and the receiving module 1002 may be implemented by a transceiver or a transceiver-related circuit component.
Fig. 15 is a schematic block diagram of a second network function network element 1100 according to an embodiment of the present application, where the second network function network element includes a receiving module 1101 and a sending module 1102.
A receiving module 1101, configured to receive a first request message sent by a first network function network element, where the first request message is used to request a first event subscription to the second network function network element, and the first request message carries an event identifier.
A sending module 1102, configured to send a first response message to the first network function network element, where the first response message carries a first identifier, and the first identifier is an identifier that is allocated to the first event subscription by the second network function network element;
The sending module 1102 is further configured to send a second request message to a third network function network element, where the second request message is used to request a second event subscription from the third network function network element for the first network function network element, and the second request message carries the event identifier and the first identifier.
Optionally, the first reply message and the second request message further carry a second identifier, where the second identifier is used to indicate the second network function network element, and the first identifier and the second identifier are used to be associated with the first event subscription.
as another embodiment, the receiving module 1101 and the sending module 1102 in the second network function network element 1100 are configured to perform the following steps:
a receiving module 1101, configured to receive a first request message sent by a first network function network element, where the first request message is used to request a first event subscription to the second network function network element, and the first request message carries an event identifier.
A sending module 1102, configured to send a second request message to a third network function network element, where the second request message carries the event identifier, and the second request message is used to request a second event subscription to the third network function network element.
The receiving module 1101 is further configured to receive a second response message sent by a third network function network element, where the second response message carries a third identifier, and the third identifier is an identifier allocated by the third network function network element to the second event subscription.
The sending module 1102 is further configured to send a first reply message to the first network function network element, where the first reply message carries the third identifier.
Optionally, the second response message and the first response message further carry a fourth identifier, where the fourth identifier is used to indicate the third network function network element, and the third identifier and the fourth identifier are used to be associated with the first event subscription.
As another embodiment, the receiving module 1101 and the sending module 1102 in the second network function network element 1100 are configured to perform the following steps:
A receiving module 1101, configured to receive a first request message sent by a first network function network element, where the first request message is used to request a first event subscription from the second network function network element, and the first request message includes an event identifier.
A sending module 1102, configured to send a first reply message to the first network function network element, where the first reply message carries a fifth identifier, and the fifth identifier is an identifier that is allocated to the first event subscription by the second network function network element.
The sending module 1102 is further configured to send a second request message to a third network function network element, where the second request message is used to request, for the first network function network element, the third network function network element for notification of an event corresponding to the event identifier, and the second request message includes the event identifier and the fifth identifier.
Optionally, the fifth identifier is an identifier of a resource created by the second network function network element for the first event subscription.
Optionally, the second request message further includes a policy rule, where the policy rule includes the event identifier and the fifth identifier.
as another embodiment, the receiving module 1101 and the sending module 1102 in the second network function network element 1100 are configured to perform the following steps:
A receiving module 1101, configured to receive a first request message sent by a first network function network element, where the first request message is used to request a first event subscription from the second network function network element, and the first request message includes an event identifier.
A sending module 1102, configured to send a first response message to the first network function network element, where the first response message carries the fifth identifier.
The sending module 1102 is further configured to send a second request message to a third network function network element, where the second request message is used to request, from the third network function network element, a notification of an event corresponding to the event identifier for the first network function network element, and the second request message carries the event identifier and a sixth identifier, where the sixth identifier is an identifier that is allocated to the first event subscription by the second network function network element.
Optionally, the sixth identifier is an identifier of a resource created by the second network function network element for the first event subscription.
Optionally, the second request message further includes a policy rule, where the policy rule includes the event identifier and the sixth identifier.
It should be understood that the transmitting module 1102 and the receiving module 1101 in the embodiments of the present invention may be implemented by a transceiver or transceiver-related circuit components.
Fig. 16 is a schematic block diagram of a third network function network element 1200 provided in an embodiment of the present application, where the third network function network element includes a receiving module 1201 and a sending module 1202.
A receiving module 1201, configured to receive a second request message sent by a second network function network element, where the second request message is used to request a second event subscription from a third network function network element to a first network function network element, the second request message carries an event identifier and a first identifier, the first identifier is an identifier allocated by the second network function network element for a first event subscription, and the first event subscription is an event subscription requested by the first network function network element to the second network function network element;
A sending module 1202, configured to send event report information to the first network function network element according to the second request message, where the event report information carries the event identifier and the first identifier.
Optionally, the second request message and the event report information further carry a second identifier, where the second identifier is used to indicate the second network function network element, and the first identifier and the second identifier are used to be associated with the first event subscription.
As another embodiment, the receiving module 1201 and the sending module 1202 in the third network functional network element 1200 are configured to perform the following steps:
A receiving module 1201, configured to receive a second request message sent by a second network function network element, where the second request message is used to request a second event subscription to the third network function network element, and the second request message carries an event identifier.
A sending module 1202, configured to send a second response message to the second network function network element according to the second request message, where the second response message carries a third identifier, and the third identifier is an identifier that is allocated by the third network function network element for the second event subscription.
The sending module 1202 is further configured to send event report information to the first network function network element, where the event report information carries the event identifier and the third identifier.
optionally, the second response message and the event report information further carry a fourth identifier, where the fourth identifier is used to indicate the third network function network element, and the third identifier and the fourth identifier are used to be associated with the first event subscription.
As another embodiment, the receiving module 1101 and the sending module 1102 in the third network function network element 1100 are configured to perform the following steps:
A receiving module 1101, configured to receive a second request message sent by a second network function network element, where the second request message is used to request, from the third network function network element, a notification of an event corresponding to an event identifier for the first network function network element, the second request message includes the event identifier and a fifth identifier, the fifth identifier is an identifier allocated by the second network function network element for a first event subscription, and the first event subscription is an event subscription requested by the first network function network element from the second network function network element.
A sending module 1102, configured to send an event notification to the first network function network element according to the second request message, where the event notification includes the event identifier and the fifth identifier.
Optionally, the fifth identifier is an identifier of a resource created by the second network function network element for the first event subscription.
Optionally, the second request message further includes a policy rule, where the policy rule includes the event identifier and the fifth identifier.
As another embodiment, the receiving module 1101 and the sending module 1102 in the third network function network element 1100 are configured to perform the following steps:
A receiving module 1101, configured to receive a second request message sent by a second network function network element, where the second request message is used to request, from the third network function network element, a notification of an event corresponding to an event identifier for the first network function network element, the second request message includes the event identifier and a sixth identifier, the sixth identifier is an identifier allocated by the second network function network element for a first event subscription, and the first event subscription is an event subscription requested by the first network function network element from the second network function network element.
a sending module 1102, configured to send an event notification to the first network function network element according to the second request message, where the event notification includes the event identifier and the sixth identifier.
Optionally, the sixth identifier is an identifier of a resource created by the second network function network element for the first event subscription.
Optionally, the second request message further includes a policy rule, where the policy rule includes the event identifier and the sixth identifier.
It should be understood that the transmitting module 1202 and the receiving module 1201 in the embodiments of the present invention may be implemented by a transceiver or a transceiver-related circuit component.
As shown in fig. 17, an embodiment of the present application further provides a first network function network element 1300, where the first network function network element 1300 includes a processor 1301, a memory 1302, and a transceiver 1303, where the memory 1302 stores instructions or programs, and the processor 1303 is configured to execute the instructions or programs stored in the memory 1302. When the instructions or programs stored in the memory 1302 are executed, the processor 1301 is configured to perform the operations performed by the processing module 1003 in the above embodiments, and the transceiver 1303 is configured to perform the operations performed by the receiving module 1002 and the sending module 1001 in the above embodiments.
As shown in fig. 18, the embodiment of the present application further provides a second network function network element 1400, where the second network function network element 1400 includes a processor 1401, a memory 1402 and a transceiver 1403, where the memory 1402 stores instructions or programs therein, and the processor 1403 is configured to execute the instructions or programs stored in the memory 1602. When the instructions or programs stored in the memory 1602 are executed, the transceiver 1403 is used for performing the operations performed by the receiving module 1101 and the transmitting module 1102 in the above embodiments.
As shown in fig. 19, the embodiment of the present application further provides a third network function network element 1500, where the first network function network element 1500 includes a processor 1501, a memory 1502 and a transceiver 1503, where the memory 1502 stores instructions or programs and the processor 1503 is configured to execute the instructions or programs stored in the memory 1502. When the instructions or programs stored in the memory 1502 are executed, the transceiver 1503 is configured to perform the operations performed by the receiving module 1201 and the sending module 1202 in the above embodiments.
It should be understood that the processor mentioned in the embodiments of the present invention may be a Central Processing Unit (CPU), and may also be other general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
It will also be appreciated that the memory referred to in this embodiment of the invention may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM, enhanced SDRAM, SLDRAM, Synchronous Link DRAM (SLDRAM), and direct rambus RAM (DR RAM).
It should be noted that when the processor is a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, the memory (memory module) is integrated in the processor.
It should be noted that the memory described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (32)

1. A method of subscribing to an event, comprising:
A first network function network element sends a first request message to a second network function network element, wherein the first request message is used for requesting a first event subscription to the second network function network element, and the first request message carries an event identifier;
The first network function network element receives a first response message sent by the second network function network element, wherein the first response message carries a first identifier, and the first identifier is an identifier which is distributed for the first event subscription by the second network function network element;
The first network function network element receives event report information sent by a third network function network element, wherein the event report information carries the event identifier and the first identifier;
And the first network function network element determines that the event report information is associated with the first event subscription according to the first identifier.
2. The method of claim 1, wherein the first reply message and the event report information further carry a second identifier, and wherein the second identifier is used for indicating the second network function network element, and wherein the first identifier and the second identifier are used for associating with the first event subscription;
The determining, by the first network function network element according to the first identifier, that the event report information is associated with the first event subscription includes:
And the first network function network element determines that the event report information is associated with the first event subscription according to the first identifier and the second identifier.
3. A method of subscribing to an event, comprising:
A second network function network element receives a first request message sent by a first network function network element, wherein the first request message is used for requesting a first event subscription to the second network function network element, and the first request message carries an event identifier;
The second network function network element sends a first response message to the first network function network element, wherein the first response message carries a first identifier, and the first identifier is an identifier which is distributed for the first event subscription by the second network function network element;
And the second network function network element sends a second request message to a third network function network element, where the second request message is used for requesting a second event subscription from the third network function network element for the first network function network element, and the second request message carries the event identifier and the first identifier.
4. The method of claim 3, wherein the first reply message and the second request message further carry a second identifier, and wherein the second identifier is used for indicating the second network function network element, and wherein the first identifier and the second identifier are used for associating with the first event subscription.
5. A method of subscribing to an event, comprising:
A third network function network element receives a second request message sent by a second network function network element, wherein the second request message is used for requesting a second event subscription from the third network function network element for a first network function network element, the second request message carries an event identifier and a first identifier, the first identifier is an identifier distributed by the second network function network element for the first event subscription, and the first event subscription is the event subscription requested by the first network function network element to the second network function network element;
And the third network function network element sends event report information to the first network function network element according to the second request message, wherein the event report information carries the event identifier and the first identifier.
6. The method of claim 5, wherein the second request message and the event report information further carry a second identifier, and wherein the second identifier is used for indicating the second network function network element, and wherein the first identifier and the second identifier are used for associating with the first event subscription.
7. A method of subscribing to an event, comprising:
A first network function network element sends a first request message to a second network function network element, wherein the first request message is used for requesting a first event subscription to the second network function network element and comprises an event identifier;
The first network function network element receives a first response message sent by the second network function network element, wherein the first response message includes a fifth identifier, and the fifth identifier is an identifier which is distributed for the first event subscription by the second network function network element;
The first network function network element receives an event notification sent by a third network function network element, wherein the event notification comprises the event identifier and the fifth identifier;
and the first network function network element determines that the event notification is associated with the first event subscription according to the fifth identifier.
8. A method of subscribing to an event, comprising:
a second network function network element receives a first request message sent by a first network function network element, wherein the first request message is used for requesting a first event subscription to the second network function network element, and the first request message comprises an event identifier;
The second network function network element sends a first reply message to the first network function network element, wherein the first reply message carries a fifth identifier, and the fifth identifier is an identifier which is distributed for the first event subscription by the second network function network element;
And the second network function network element sends a second request message to a third network function network element, where the second request message is used for requesting, by the first network function network element, a notification of an event corresponding to the event identifier from the third network function network element, and the second request message includes the event identifier and the fifth identifier.
9. A method of event subscription, comprising:
A third network function network element receives a second request message sent by a second network function network element, wherein the second request message is used for requesting, from the third network function network element, a notification of an event corresponding to an event identifier for a first network function network element, the second request message includes the event identifier and a fifth identifier, the fifth identifier is an identifier allocated by the second network function network element for a first event subscription, and the first event subscription is an event subscription requested by the first network function network element to the second network function network element;
and the third network function network element sends an event notification to the first network function network element according to the second request message, wherein the event notification comprises the event identifier and the fifth identifier.
10. The method according to any of claims 7 to 9, wherein the fifth identity is an identity of a resource created by the second network function network element for the first event subscription.
11. The method according to any of claims 8 to 10, the second request message further comprising a policy rule including the event identification and the fifth identification.
12. A method of subscribing to an event, comprising:
A first network function network element sends a first request message to a second network function network element, wherein the first request message is used for requesting a first event subscription to the second network function network element and comprises an event identifier;
The first network function network element receives a first response message sent by the second network function network element, wherein the first response message carries a fifth identifier;
The first network function network element acquires a sixth identifier according to the fifth identifier, wherein the sixth identifier is an identifier which is distributed for the first event subscription by the second network function network element;
The first network function network element receives an event notification sent by a third network function network element, wherein the event notification comprises the event identifier and the sixth identifier;
And the first network function network element determines that the event notification is associated with the first event subscription according to the sixth identifier.
13. A method of subscribing to an event, comprising:
A second network function network element receives a first request message sent by a first network function network element, wherein the first request message is used for requesting a first event subscription to the second network function network element, and the first request message comprises an event identifier;
The second network function network element sends a first response message to the first network function network element, wherein the first response message carries a fifth identifier;
The second network function network element sends a second request message to a third network function network element, where the second request message is used to request, from the third network function network element, a notification of an event corresponding to the event identifier for the first network function network element, and the second request message carries the event identifier and a sixth identifier, where the sixth identifier is an identifier that is distributed by the second network function network element for the first event subscription.
14. a method of subscribing to an event, comprising:
a third network function network element receives a second request message sent by a second network function network element, wherein the second request message is used for requesting, by the first network function network element, a notification of an event corresponding to an event identifier from the third network function network element, the second request message includes the event identifier and a sixth identifier, the sixth identifier is an identifier allocated by the second network function network element for a first event subscription, and the first event subscription is an event subscription requested by the first network function network element from the second network function network element;
And the third network function network element sends an event notification to the first network function network element according to the second request message, wherein the event notification comprises the event identifier and the sixth identifier.
15. The method according to any of claims 12 to 14, wherein the sixth identity is an identity of a resource created by the second network function network element for the first event subscription.
16. The method according to any of claims 13 to 15, the second request message further comprising a policy rule including the event identification and the sixth identification.
17. A first network functional network element, comprising:
a sending module, configured to send a first request message to a second network function network element, where the first request message is used to request a first event subscription to the second network function network element, and the first request message carries an event identifier;
A receiving module, configured to receive a first response message sent by the second network function network element, where the first response message carries a first identifier, and the first identifier is an identifier that is distributed by the second network function network element for the first event subscription;
The receiving module is further configured to receive event report information sent by a third network function network element, where the event report information carries the event identifier and the first identifier;
And the processing module is used for determining that the event report information is associated with the first event subscription according to the first identifier.
18. The first network functional network element according to claim 17, wherein the first reply message and the event report information further carry a second identifier, the second identifier being used to indicate the second network functional network element, wherein the first identifier and the second identifier are used to associate with the first event subscription;
The processing module is further configured to: determining that the event reporting information is associated with the first event subscription based on the first identifier and the second identifier.
19. A second network functional network element, comprising:
A receiving module, configured to receive a first request message sent by a first network function network element, where the first request message is used to request a first event subscription to a second network function network element, and the first request message carries an event identifier;
a sending module, configured to send a first response message to the first network function network element, where the first response message carries a first identifier, and the first identifier is an identifier that is distributed by the second network function network element for the first event subscription;
The sending module is further configured to send a second request message to a third network function network element, where the second request message is used to request a second event subscription from the third network function network element for the first network function network element, and the second request message carries the event identifier and the first identifier.
20. The second network functional network element according to claim 19, wherein the first reply message and the second request message further carry a second identifier, the second identifier being used to indicate the second network functional network element, wherein the first identifier and the second identifier are used to associate with the first event subscription.
21. A third network functional network element, comprising:
A receiving module, configured to receive a second request message sent by a second network function network element, where the second request message is used to request a second event subscription from a third network function network element to a first network function network element, the second request message carries an event identifier and a first identifier, the first identifier is an identifier allocated by the second network function network element for a first event subscription, and the first event subscription is an event subscription requested by the first network function network element to the second network function network element;
And a sending module, configured to send event report information to a first network function network element according to the second request message, where the event report information carries the event identifier and the first identifier.
22. The third network functional network element according to claim 21, wherein the second request message and the event report information further carry a second identifier, and the second identifier is used to indicate the second network functional network element, and wherein the first identifier and the second identifier are used to associate with the first event subscription.
23. A first network functional network element, comprising:
A sending module, configured to send a first request message to a second network function network element, where the first request message is used to request a first event subscription to the second network function network element, and the first request message includes an event identifier;
A receiving module, configured to receive a first response message sent by the second network function network element, where the first response message includes a fifth identifier, and the fifth identifier is an identifier that is allocated to the first event subscription by the second network function network element;
The receiving module is further configured to receive an event notification sent by a third network function network element, where the event notification includes the event identifier and the fifth identifier;
And the processing module is used for determining that the event notification is associated with the first event subscription according to the fifth identifier.
24. A second network functional network element, comprising:
A receiving module, configured to receive a first request message sent by a first network function network element, where the first request message is used to request a first event subscription to a second network function network element, and the first request message includes an event identifier;
A sending module, configured to send a first reply message to the first network function network element, where the first reply message carries a fifth identifier, and the fifth identifier is an identifier that is distributed by the second network function network element for the first event subscription;
The sending module is further configured to send a second request message to a third network function network element, where the second request message is used to request, by the first network function network element, the third network function network element for notification of an event corresponding to the event identifier, and the second request message includes the event identifier and the fifth identifier.
25. A third network functional network element, comprising:
a receiving module, configured to receive a second request message sent by a second network function network element, where the second request message is used to request, from a first network function network element to a third network function network element, a notification of an event corresponding to an event identifier, where the second request message includes the event identifier and a fifth identifier, the fifth identifier is an identifier allocated by the second network function network element for a first event subscription, and the first event subscription is an event subscription requested by the first network function network element to the second network function network element;
A sending module, configured to send an event notification to a first network function network element according to the second request message, where the event notification includes the event identifier and the fifth identifier.
26. a network functional network element as claimed in any of claims 23 to 25, wherein the fifth identity is an identity of a resource created by the second network functional network element for the first event subscription.
27. The network functional network element according to any of claims 24 to 26, the second request message further comprising a policy rule including the event identification and the fifth identification.
28. A first network functional network element, comprising:
A sending module, configured to send a first request message to a second network function network element, where the first request message is used to request a first event subscription to the second network function network element, and the first request message includes an event identifier;
A receiving module, configured to receive a first response message sent by the second network functional network element, where the first response message carries a fifth identifier;
a processing module, configured to obtain a sixth identifier according to the fifth identifier, where the sixth identifier is an identifier that is distributed by the second network function network element for the first event subscription;
The receiving module is further configured to receive an event notification sent by a third network function network element, where the event notification includes the event identifier and the sixth identifier;
The processing module is further configured to determine that the event notification is associated with the first event subscription according to the sixth identifier.
29. A second network functional network element, comprising:
A receiving module, configured to receive a first request message sent by a first network function network element, where the first request message is used to request a first event subscription to a second network function network element, and the first request message includes an event identifier;
A sending module, configured to send a first response message to the first network functional network element, where the first response message carries a fifth identifier;
The sending module is further configured to send a second request message to a third network function network element, where the second request message is used to request, by the first network function network element, the third network function network element for notification of an event corresponding to the event identifier, the second request message carries the event identifier and a sixth identifier, and the sixth identifier is an identifier that is distributed by the second network function network element for subscription of the first event.
30. A third network functional network element, comprising:
A receiving module, configured to receive a second request message sent by a second network function network element, where the second request message is used to request, from a first network function network element to a third network function network element, a notification of an event corresponding to an event identifier, where the second request message includes the event identifier and a sixth identifier, the sixth identifier is an identifier allocated by the second network function network element for a first event subscription, and the first event subscription is an event subscription requested by the first network function network element to the second network function network element;
A sending module, configured to send an event notification to a first network function network element according to the second request message, where the event notification includes the event identifier and the sixth identifier.
31. A network functional network element as claimed in any of claims 28 to 30, wherein the sixth identity is an identity of a resource created by the second network functional network element for the first event subscription.
32. The network functional network element of any of claims 29 to 31, the second request message further comprising a policy rule including the event identification and the sixth identification.
CN201811161672.5A 2018-05-31 2018-09-30 Method for subscribing event and network function network element Active CN110557744B (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810551171 2018-05-31
CN2018105511711 2018-05-31

Publications (2)

Publication Number Publication Date
CN110557744A true CN110557744A (en) 2019-12-10
CN110557744B CN110557744B (en) 2022-08-19

Family

ID=68736184

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201811161672.5A Active CN110557744B (en) 2018-05-31 2018-09-30 Method for subscribing event and network function network element

Country Status (1)

Country Link
CN (1) CN110557744B (en)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021185303A1 (en) * 2020-03-18 2021-09-23 维沃移动通信有限公司 Method for subscribing to network event and network functions
CN113573282A (en) * 2020-04-29 2021-10-29 中国电信股份有限公司 Subscription data providing/acquiring method, providing/acquiring device and interactive system
CN114915617A (en) * 2021-02-10 2022-08-16 华为技术有限公司 HTTP updating method and communication device
CN115152253A (en) * 2020-01-03 2022-10-04 索尼集团公司 Reporting service of dynamic state information on data links
WO2022218725A1 (en) * 2021-04-13 2022-10-20 Telefonaktiebolaget Lm Ericsson (Publ) Supporting compatibility
WO2023133858A1 (en) * 2022-01-14 2023-07-20 北京小米移动软件有限公司 Access type-based slice event subscription reporting methods and apparatus, and storage medium
WO2023134493A1 (en) * 2022-01-17 2023-07-20 华为技术有限公司 Communication method and apparatus
WO2023143437A1 (en) * 2022-01-27 2023-08-03 维沃移动通信有限公司 Information disclosure method and communication device
WO2024021582A1 (en) * 2022-07-29 2024-02-01 中兴通讯股份有限公司 Network data plane system, data interaction method, and storage medium

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104581670A (en) * 2013-10-15 2015-04-29 中兴通讯股份有限公司 Application access control method and application function physical device
CN106973118A (en) * 2017-05-12 2017-07-21 京东方科技集团股份有限公司 Generation and the method and apparatus of subscribing notification
US9722856B2 (en) * 2014-09-18 2017-08-01 Tech Mahindra Ltd. System and method to orchestrate and control sequence of recovery actions for resumption of business services by dynamically changing recovery action sequence based on feedback received from agent/open flow based devices catering to both traditional and software defined networks
CN107431722A (en) * 2015-03-09 2017-12-01 瑞典爱立信有限公司 The dynamic event of M2M communication is subscribed to

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104581670A (en) * 2013-10-15 2015-04-29 中兴通讯股份有限公司 Application access control method and application function physical device
US9722856B2 (en) * 2014-09-18 2017-08-01 Tech Mahindra Ltd. System and method to orchestrate and control sequence of recovery actions for resumption of business services by dynamically changing recovery action sequence based on feedback received from agent/open flow based devices catering to both traditional and software defined networks
CN107431722A (en) * 2015-03-09 2017-12-01 瑞典爱立信有限公司 The dynamic event of M2M communication is subscribed to
CN106973118A (en) * 2017-05-12 2017-07-21 京东方科技集团股份有限公司 Generation and the method and apparatus of subscribing notification

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI等: "Subscription status notification for Event Exposure service", 《3GPP TSG-SA WG2 MEETING #127 S2-183998》 *
NOKIA 等: "Improvements on the specification of the subscription to Network Exposure", 《SA WG2 MEETING #125 S2-181268》 *

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115152253B (en) * 2020-01-03 2024-03-15 索尼集团公司 Reporting services for dynamic state information over data links
CN115152253A (en) * 2020-01-03 2022-10-04 索尼集团公司 Reporting service of dynamic state information on data links
CN113498051A (en) * 2020-03-18 2021-10-12 维沃移动通信有限公司 Method for subscribing network event and network function
WO2021185303A1 (en) * 2020-03-18 2021-09-23 维沃移动通信有限公司 Method for subscribing to network event and network functions
CN113573282A (en) * 2020-04-29 2021-10-29 中国电信股份有限公司 Subscription data providing/acquiring method, providing/acquiring device and interactive system
CN113573282B (en) * 2020-04-29 2022-09-16 中国电信股份有限公司 Subscription data providing/acquiring method, providing/acquiring device and interactive system
CN114915617A (en) * 2021-02-10 2022-08-16 华为技术有限公司 HTTP updating method and communication device
WO2022218725A1 (en) * 2021-04-13 2022-10-20 Telefonaktiebolaget Lm Ericsson (Publ) Supporting compatibility
CN117044248A (en) * 2022-01-14 2023-11-10 北京小米移动软件有限公司 Method, device and storage medium for reporting slice event subscription based on access type
WO2023133858A1 (en) * 2022-01-14 2023-07-20 北京小米移动软件有限公司 Access type-based slice event subscription reporting methods and apparatus, and storage medium
WO2023134493A1 (en) * 2022-01-17 2023-07-20 华为技术有限公司 Communication method and apparatus
WO2023143437A1 (en) * 2022-01-27 2023-08-03 维沃移动通信有限公司 Information disclosure method and communication device
WO2024021582A1 (en) * 2022-07-29 2024-02-01 中兴通讯股份有限公司 Network data plane system, data interaction method, and storage medium

Also Published As

Publication number Publication date
CN110557744B (en) 2022-08-19

Similar Documents

Publication Publication Date Title
CN110557744B (en) Method for subscribing event and network function network element
CN110383790B (en) Network service continuity without session continuity
CN112637947B (en) Base station, access and mobility management functional entity and method thereof
KR102456859B1 (en) Method and apparatus for provisioning service parameters to the ue and the network in 5g system
CN115460685A (en) Base station, access and mobility management functional entity and method thereof
CN113630749B (en) Method and device for acquiring edge service
CN108781361B (en) Method and apparatus for processing data packets
WO2019220172A1 (en) Token-based debugging for a service-based architecture
US11659621B2 (en) Selection of IP version
KR20180038304A (en) Ue attach and pdu session setup in the visited plmn supporting network slice
JP2022529234A (en) Systems and methods for handling the telescopic FQDN
KR20170063931A (en) Methods for restricted direct discovery
US10334659B2 (en) System and method for group device access to wireless networks
CN111615844B (en) Method and apparatus for selecting a session management entity serving a wireless communication device
CN113382468B (en) Address allocation method for local network device, electronic device, and storage medium
CN109155734B (en) Key generation and distribution method based on identity identification cryptographic technology
WO2015120480A1 (en) Extending connectivity in a machine to machine communication system
WO2020217224A1 (en) Amf and scp behavior in delegated discovery of pcf
US9560583B2 (en) Gateway selection based on geographical location
US11228896B2 (en) Authorization of roaming for new radio subscribers via an alternative radio access technology
KR20220069875A (en) Method and device for acquiring vehicle-to-X communication strategy
WO2022061675A1 (en) Data analysis method and apparatus
WO2023060408A1 (en) Sensing data collection method and apparatus, and device, system and storage medium
CN116866965A (en) Backup method, communication device and communication system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant