CN113596781B

CN113596781B - Subscription method, service network element and user data management network element

Info

Publication number: CN113596781B
Application number: CN202010369961.5A
Authority: CN
Inventors: 孙万飞; 胡渭琦; 徐晖
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2020-04-30
Filing date: 2020-04-30
Publication date: 2022-06-07
Anticipated expiration: 2040-04-30
Also published as: CN113596781A

Abstract

The embodiment of the invention provides a subscription method, a service network element and a user data management network element, wherein the method comprises the following steps: sending a first request message to a user data management network element, wherein the first request message is a registration request message or a subscription data request message, and the first request message carries first subscription context information to indicate subscription requirements; and receiving a first response message fed back by the user data management network element based on the first request message, wherein the first response message is a registration request response message or a subscription data request response message, and the first response message carries second subscription context information to indicate a subscription result corresponding to the subscription requirement. The embodiment of the invention reduces the signaling interaction quantity in the registration or session establishment flow.

Description

Subscription method, service network element and user data management network element

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a subscription method, a service network element, and a user data management network element.

Background

In a mobile communication system, when a terminal registers in a network or establishes a session, a service network element needs to register in a Unified Data Manager (user Data Manager) to acquire subscription Data and subscribe to a related service; and when the terminal registers, releases the session or the released session belongs to a certain granularity or meets a certain condition, the service network element needs to unsubscribe the relevant service subscribed to the user data management network element.

In the current mobile communication system, in the registration process or session establishment process, the service network element initiates registration to the user data management network element, acquires the subscription data, and then initiates the subscription process; in the process of deregistration or session release, the service network element deregisters with the user data management network element and then initiates a unsubscribing process, and before initiating the unsubscribing, the service network element needs to judge the session, judge whether the session belongs to a certain granularity or meets a certain condition, and initiate the unsubscribing to the user data management network element.

In summary, the process of registering/acquiring the subscription data from the user data management network element by the service network element is complicated, the flow is time-consuming, the process of subscription determination is complicated, the time consumption is long, and the overhead of the service network element operation load is high.

Disclosure of Invention

The embodiment of the invention provides a subscription method, a service network element and a user data management network element, so as to reduce the flow steps in the subscription process.

The embodiment of the invention provides a subscription method, which is applied to a service network element and comprises the following steps:

sending a first request message to a user data management network element, wherein the first request message is a registration request message or a subscription data request message, and the first request message carries first subscription context information to indicate subscription requirements;

And receiving a first response message fed back by the user data management network element based on the first request message, wherein the first response message is a registration request response message or a subscription data request response message, and the first response message carries second subscription context information to indicate a subscription result corresponding to the subscription requirement.

The embodiment of the invention provides a subscription method, which is applied to a user data management network element and comprises the following steps:

receiving a first request message sent by a service network element, wherein the first request message is a registration request message or a subscription data request message and carries first subscription context information to indicate subscription requirements;

and feeding back a first response message to the serving network element based on the first request message, wherein the first response message is a registration request response message or a subscription data request response message, and the first response message carries second subscription context information to indicate a subscription result corresponding to the subscription requirement.

The embodiment of the invention provides a subscription device, which is applied to a service network element and comprises the following components:

a sending module, configured to send a first request message to a user data management network element, where the first request message is a registration request message or a subscription data request message, and the first request message carries first subscription context information to indicate a subscription requirement;

A receiving module, configured to receive a first response message fed back by the user data management network element based on the first request message, where the first response message is a registration request response message or a subscription data request response message, and the first response message carries second subscription context information to indicate a subscription result corresponding to the subscription requirement.

The embodiment of the invention provides a subscription device, which is applied to a user data management network element and comprises the following components:

a receiving module, configured to receive a first request message sent by a serving network element, where the first request message is a registration request message or a subscription data request message, and the first request message carries first subscription context information to indicate a subscription requirement;

a sending module, configured to feed back a first response message to the serving network element based on the first request message, where the first response message is a registration request response message or a subscription data request response message, and the first response message carries second subscription context information to indicate a subscription result corresponding to the subscription requirement.

The embodiment of the invention provides a service network element, which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein the steps of the subscription method are realized when the processor executes the program.

The embodiment of the invention provides a user data management network element, which comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor executes the program to realize the steps of the subscription method.

Embodiments of the present invention provide a non-transitory computer-readable storage medium, on which a computer program is stored, which, when executed by a processor, implements the steps of the subscription method.

According to the subscription method, the service network element and the user data management network element provided by the embodiment of the invention, the subscription function is completed by establishing a subscription context mechanism and carrying the subscription context information in other signaling by sending the first request message to the user data management network element while carrying the first subscription context information for indicating the subscription requirement, and receiving the first response message fed back by the user data management network element based on the first request message, and carrying the second subscription context information for indicating the subscription result corresponding to the subscription requirement in the first response message, so that the subscription process specially initiated by the service network element to the user data management network element is omitted, the signaling quantity of the signaling process is reduced, the time consumption of the process is effectively reduced, and the operation load of the service network element is reduced.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and those skilled in the art can also obtain other drawings according to the drawings without creative efforts.

Fig. 1 is a flowchart illustrating steps of a subscription method applied to a serving network element according to an embodiment of the present invention;

fig. 2 is a flowchart illustrating steps of a subscription method applied to a subscriber data management network element according to an embodiment of the present invention;

FIG. 3 is a schematic flow chart of a first embodiment of the present invention;

FIG. 4 is a schematic flow chart of a second embodiment of the present invention;

FIG. 5 is a flow chart illustrating a third embodiment of the present invention;

FIG. 6 is a schematic flow chart of a fourth embodiment of the present invention;

FIG. 7 is a schematic flow chart of a fifth embodiment of the present invention;

fig. 8 is a block diagram of a subscription apparatus applied to a serving network element in an embodiment of the present invention;

fig. 9 is a block diagram of a subscription apparatus applied to a subscriber data management network element in an embodiment of the present invention;

fig. 10 is a schematic structural diagram of a serving network element in an embodiment of the present invention;

Fig. 11 is a schematic structural diagram of a user data management network element in an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

For the convenience of clearly describing the technical solutions of the embodiments of the present invention, in each embodiment of the present invention, if words such as "first" and "second" are used to distinguish the same items or similar items with basically the same functions and actions, those skilled in the art can understand that the words such as "first" and "second" do not limit the quantity and execution order.

The term "and/or" in the embodiments of the present invention describes an association relationship of associated objects, and indicates that three relationships may exist, for example, a and/or B may indicate: a exists alone, A and B exist simultaneously, and B exists alone. The character "three types" generally indicates that the former and latter associated objects are in an "or" relationship.

The term "plurality" in the embodiments of the present invention means two or more, and other terms are similar thereto.

Furthermore, it should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

In various embodiments of the present invention, it should be understood that the sequence numbers of the following processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.

In the registration process, an Access and Mobility Management Function (AMF) first registers with a UDM network element, then the AMF initiates a process of acquiring subscription data to the UDM, and finally the AMF subscribes related information to the UDM. In a Session establishment process initiated by a terminal, an AMF establishes a Session Management context with a Session Management Function (SMF), the SMF obtains subscription data from a UDM, and then the SMF subscribes related information from the UDM. In the de-registration process, initiated by a terminal or a network, SMF initiates de-registration to UDM after initiating de-subscription to UDM, and AMF initiates de-registration to UDM after initiating de-subscription to UDM. In the session release process, initiated by the terminal or the network, the SMF initiates de-subscription to the UDM and then initiates de-registration.

Namely, in the registration process and the session establishment process, the service network element registers and subscribes to the UDM; in the deregistration process and the session release process, after unsubscribing to the UDM, the service network element deregisters to the UDM, and in the session release process, it needs to be judged whether the session being served is the last session of a session with a certain granularity (or a session meeting a certain condition), and if the session is the last session (or meeting a certain condition), the service network element initiates unsubscription to the UDM.

However, in the registration or session establishment process, the service network element registration and subscription are performed in two steps, which takes a long time; in the flow of deregistration and session release, the deregistration and the deregistration are executed in two steps, and in the flow of session release, the service network element needs to judge whether the session is the last session under a certain granularity or meets a certain condition, so that the time consumption, the complexity and the overhead of the operation load of the service network element are large.

In view of the above-mentioned drawbacks, the present invention provides the following embodiments:

as shown in fig. 1, it is a flowchart of steps of a subscription method applied to a serving network element in an embodiment of the present invention, where the method includes the following steps:

step 101: the first request message is sent to a user data management network element.

Specifically, the first request message is a registration request message or a subscription data request message, and the first request message carries first subscription context information to indicate a subscription requirement.

Namely, the service network element carries the first subscription context information for indicating the subscription requirement when sending the registration request message to the user data management network element, or carries the first subscription context information for indicating the subscription requirement when sending the subscription data request message to the user data management network element, so that the subscription function can be realized through the registration step or the signed data acquisition step, the subscription step of the service network element to the user data management network element is omitted, the signaling quantity of the signaling flow in the registration process or the session establishment process is reduced, the time consumption of the flow is effectively reduced, and the operation load of the service network element is reduced.

Furthermore, it should be noted that the user data management network element may be a UDM network element.

Step 102: and receiving a first response message fed back by the user data management network element based on the first request message.

Specifically, the first response message is a registration request response message or a subscription data request response message, and the first response message carries the second subscription context information to indicate a subscription result corresponding to the subscription requirement.

Of course, the subscription result may be that the subscription is completed or that the subscription is not completed.

That is, after receiving the first request message sent by the serving network element, the user data management network element may feed back the first response message based on the first request message, and the first response message carries the second subscription context information used for indicating the subscription result corresponding to the subscription requirement, thereby implementing the function of completing the subscription result feedback through the registration response step or the subscription data acquisition response step.

In this way, the serving network element in this embodiment carries the first subscription context information for indicating the subscription requirement when sending the first request message to the user data management network element, and receives the first response message fed back by the user data management network element based on the first request message, and carries the second subscription context information for indicating the subscription result corresponding to the subscription requirement in the first response message.

It should be noted that, when sending the first request message to the user data management network element, when performing registration, the serving network element is a mobility management network element, and sends a registration request message or a subscription data request message carrying the first subscription context information to the user data management network element; and/or, when the session is established, the service network element is a session management network element, and sends a subscription data request message carrying the first subscription context information to the user data management network element.

Specifically, the mobility management network element may be an AMF network element, and the session management network element may be an SMF network element.

Specifically, in the terminal registration flow, in the process of subscribing the service network element to the user data management network element, the service network element is a mobility management network element, and at this time, the service network element can carry the first subscription context information when registering or acquiring the subscription data to the user data management network element, that is, the service network element can carry the first subscription context information in the registration request message or the subscription data request message, so that the subscription function is realized when requesting to register or acquire the subscription data in the registration flow, and further, the subscription process specially initiated by the service network element to the user data management network element is omitted, and the signaling number of the signaling flow is reduced.

In addition, in the initiated session establishment flow, the service network element is a session management network element, and at this time, the service network element may carry the first subscription context information when acquiring the subscription data from the user data management network element, that is, the service network element may carry the first subscription context information in the subscription data request message, thereby implementing the subscription function when acquiring the subscription data, further omitting the subscription process specifically initiated by the service network element to the user data management network element in the session establishment flow, and reducing the signaling number of the signaling flow.

Further, on the basis of the foregoing embodiment, when the serving network element receives the first response message fed back by the user data management network element based on the first request message, the serving network element may receive, when the serving network element is a mobility management network element, a registration request response message fed back by the user data management network element based on the registration request message or a subscription data request response message fed back by the subscription data request message; and/or when the service network element is the session management network element, receiving a subscription data request response message fed back by the user data management network element based on the subscription data request message.

When the user data management network element receives the subscription data request message sent by the session management network element, the subscription data request response message carrying the second subscription context information is fed back to the session management network element, and when the user data management network element receives the subscription data request message sent by the mobility management network element, the subscription data request response message carrying the second subscription context information is fed back to the session management network element, so that the subscription context information identifying the subscription result is carried in the corresponding response message, and the subscription function is completed.

Furthermore, in this embodiment, after receiving a first response message fed back by the user data management network element based on the first request message, the serving network element may also send a second request message to the user data management network element, where the second request message is a deregistration request message, and the deregistration request message carries third subscription context information to indicate a deregistration requirement; and receiving a second response message fed back by the user data management network element based on the second request message, wherein the second response message is a de-registration request response message and carries fourth subscription context information to indicate a de-subscription result corresponding to the de-subscription requirement, and the de-subscription result comprises that de-subscription is completed or is not completed.

That is, in this embodiment, the third subscription context information for indicating the unsubscribing requirement may be carried in the deregistration request message, and the fourth subscription context information for indicating the unsubscribing result corresponding to the unsubscribing requirement may be carried in the deregistration request response message, so that the unsubscribing step is omitted in the deregistration process or the session release process, the signaling number of the signaling flow is reduced, the consumption of the flow is effectively reduced, and the operation load of the service network element is reduced.

Specifically, when performing de-registration, the serving network elements are a mobility management network element and a session management network element, that is, in a de-registration process initiated by a terminal or a network, the mobility management network element and the session management network element may carry third subscription context information for indicating a de-subscription requirement in a de-registration request message sent to the user data management network element, so as to save a de-subscription step in the de-registration process; and receiving a deregistration request response message fed back by the user data management network element based on the deregistration request message, and carrying fourth subscription context information indicating a unsubscribing result corresponding to the unsubscribing requirement in the deregistration request response message to complete the unsubscribing function.

When the session is released, the service network element is a session management network element, when the user data management network element determines that the current session meets the preset condition, the unsubscribing result is that unsubscribing is completed, and when the user data management network element determines that the current session does not meet the preset condition, the unsubscribing result is that unsubscribing is not completed.

Specifically, the preset condition may be that the current session is the last session of a session with a certain granularity, and the preset condition is not specifically limited herein.

Therefore, in the session release process, the session management network element does not need to judge whether the current session in service meets the preset conditions, for example, whether the current session is the last session of a session with a certain granularity, but can directly carry the third subscription context information for indicating the subscription removal requirement when sending the registration removal request message to the network friend of the user data management network element, so that the step that the session management network element judges whether the current session meets the preset conditions is omitted, and the step of subscription removal is omitted. In addition, after receiving the deregistration request message, the user data management network element can judge whether the current session meets a preset condition, and at the moment, if the current session is determined to meet the preset condition, the deregistration request response message can carry a unsubscribing result which is finished to the deregistration, and if the current session is determined to not meet the preset condition, the deregistration request response message carries an unsubscribing result which is not finished to the deregistration; that is, compared with the prior art, the service network element does not determine whether the current session meets the preset condition any more, but determines whether the current session meets the preset condition and gives the unsubscribe result indicating whether the current session is completed through the user data management network element, thereby reducing the operation load of the service network element.

Of course, it should be noted herein that after receiving the first response message fed back by the user data management network element based on the first request message, the serving network element may also send a third request message to the user data management network element, where the third request message carries fifth subscription context information to indicate a subscription update requirement; and then receiving a third response message fed back by the user data management network element based on the third request message, wherein the third response message carries sixth subscription context information to indicate a subscription update result corresponding to the subscription update requirement.

Specifically, the update requirement may be modification, deletion, and the like, and is not specifically limited herein.

That is, when the subscription information needs to be updated, such as modified and deleted, the corresponding function can be completed by carrying the subscription context information in other signaling.

In addition, in this embodiment, the serving network element may further send a fourth request message to the other serving network elements, where the fourth request message carries seventh subscription context information to indicate a subscription, unsubscribe, or subscription update requirement; and receiving a fourth response message fed back by the other service network elements based on the fourth request message, wherein the fourth response message carries eighth subscription context information to indicate a subscription, unsubscribe or subscription update result corresponding to the subscription, unsubscribe or subscription update requirement.

That is, the seventh subscription context information may be carried in other message signaling in the subscription process between the serving network element and another network element in this embodiment, so that in the subscription process between the serving network element and another network element, the subscription, unsubscribe, or subscription update signaling is combined with other signaling, and further, by using a mechanism in which the subscription context is carried in signaling in another flow, a simplified process of combining signaling in a flow is realized, that is, by carrying other signaling content information in the flow in signaling in one flow, the number of signaling interactions is reduced.

It should be noted that, the signaling in one flow carries other signaling content information in the flow, and the signaling can be applied to multiple flows, which is not illustrated here.

In this way, the service network element in this embodiment sends, to the user data management network element, the first request message carrying the first subscription context information for indicating the subscription requirement, and receives, from the user data management network element, the first response message fed back based on the first request message, and carries, in the first response message, the second subscription context information for indicating the subscription result corresponding to the subscription requirement, so that the subscription function is completed by establishing the subscription context mechanism and carrying the subscription context information in other signaling, thereby omitting the subscription process that the service network element specially initiates to the user data management network element, reducing the signaling number of the signaling flow, effectively reducing the time consumption of the flow, and reducing the operation load of the service network element.

Furthermore, as shown in fig. 2, it is a flowchart of the steps of the subscription method applied to the user data management network element, and the method includes the following steps:

step 201: receiving a first request message sent by a service network element.

Step 202: and feeding back the first response message to the service network element based on the first request message.

It should be noted that, the above process may refer to corresponding content on the serving network element side, and is not described herein again.

Further, when the user data management network element receives the first request message sent by the serving network element, it may receive a registration request message or a subscription data request message carrying first subscription context information sent by the mobility management network element during registration; and/or receiving a subscription data request message carrying first subscription context information, which is sent by a session management network element when a session is established.

In addition, when the subscriber data management network element feeds back the first response message to the serving network element based on the first request message, the registration request response message may be fed back to the mobility management network element based on the registration request message, or the subscription data request response message may be fed back to the mobility management network element based on the subscription data request message; and/or feeding back the signing data request response message to the session management network element based on the signing data request message.

The above specific process may refer to related contents in the serving network element side embodiment, and is not described herein again.

In addition, further, after feeding back the first response message to the serving network element based on the first request message, the user data management network element may further receive a second request message sent by the serving network element, where the second request message is a de-registration request message, and the de-registration request message carries third subscription context information to indicate a de-subscription requirement; feeding back a second response message to the service network element based on the second request message, wherein the second response message is a de-registration request response message and carries fourth subscription context information to indicate a de-subscription result corresponding to the de-subscription requirement; the unsubscribe result comprises that the unsubscribe is completed or the unsubscribe is not completed.

Specifically, when deregistering, the service network element is a mobility management network element and a session management network element; when the session is released, the service network element is a session management network element, when the user data management network element determines that the current session meets the preset condition, the unsubscribing result is that unsubscribing is completed, and when the user data management network element determines that the current session does not meet the preset condition, the unsubscribing result is that unsubscribing is not completed.

For the above specific unsubscribe process, reference may be made to the specific contents of the embodiment at the serving network element side, which are not described herein again.

In this way, the user data management network element in this embodiment receives a first request message that is sent by the serving network element and carries first subscription context information indicating a subscription requirement, and feeds back a first response message to the serving network element based on the first request message, and carries second subscription context information for indicating a subscription result corresponding to the subscription requirement in the first response message, thereby implementing that a subscription context mechanism is established, and subscription context information is carried in other signaling to complete a subscription function, thereby omitting a subscription process that is initiated by the serving network element to the user data management network element, reducing the signaling number of a signaling flow, effectively reducing the time consumption of the flow, and reducing the operation load of the serving network element.

The present invention will be specifically described below with reference to specific examples.

The first embodiment:

it is assumed that in this embodiment, the serving network element is an AMF network element, and the user data management network element is a UDM network element. As shown in fig. 3, in a process that a serving network element subscribes to a UDM network element in a registration flow initiated by a terminal (UE), an AMF network element sends a registration request message to the UDM network element, and carries first subscription context information used for indicating subscription requirements; and the UDM network element feeds back a registration request response message to the AMF network element based on the registration request message carrying the first subscription context information, and carries the second subscription context information in the registration request response message, and identifies a subscription result. Of course, after receiving the registration request response message, the AMF network element may obtain the subscription data from the UDM network element according to the normal registration flow, and receive a response of obtaining the subscription data fed back by the UDM network element.

In the embodiment, the subscription step and the registration step in the existing registration flow are combined, so that the subscription function to the UDM network element is realized by carrying the subscription context information in the registration related signaling, and the signaling interaction quantity in the registration flow is reduced.

Second embodiment:

it is assumed that in this embodiment, the serving network element is an AMF network element, and the user data management network element is a UDM network element. As shown in fig. 4, in a registration process initiated by a terminal (UE), an AMF network element registers with a UDM network element according to a normal registration process, and receives a registration response fed back by a DUM network element; then, the AMF network element sends a signing data request message to the UDM network element, and carries first subscription context information used for indicating subscription requirements; and the UDM network element feeds back a signing data request response message to the AMF network element based on the signing data request message carrying the first subscription context information, and carries the second subscription context information in the signing data request response message, and identifies a subscription result.

In the embodiment, the subscription step and the subscription data acquisition step in the existing registration process are combined, so that the subscription function to the UDM network element is realized by carrying the subscription context information in the signaling related to the subscription data acquisition, and the signaling interaction quantity in the registration process is reduced.

In the first embodiment and the second embodiment, it is realized that the first subscription context information may be carried when the registration request message is sent, or the first subscription context information may be carried when the subscription data request message is sent, which is not limited specifically herein.

The third embodiment:

in this embodiment, the service network element is an SMF network element, and the user data management network element is an UDM network element. As shown in fig. 5, in a session establishment procedure initiated by a terminal (UE), in a process in which a serving network element subscribes to a UDM network element, an AMF network element creates a session management context with an SMF network element according to a normal procedure; then, the SMF network element sends a signing data request message to the UDM network element, and carries first subscription context information used for indicating subscription requirements; and the UDM network element feeds back a signing data request response message to the SMF network element based on the signing data request message carrying the first subscription context information, carries the second subscription context information in the signing data request response message and identifies a subscription result.

In the embodiment, the subscription step in the existing session establishment flow is combined with the step of acquiring the subscription data, so that the subscription function to the UDM network element is realized by carrying the subscription context information in the signaling related to the acquisition of the subscription data.

The fourth embodiment:

in this embodiment, the service network elements are an AMF network element and an SMF network element, and the user data management network element is a UDM network element. As shown in fig. 6, in a deregistration process initiated by a terminal (UE) or a network, a serving network element performs a unsubscribe process to a UDM network element, and an SMF network element sends a deregistration request message to the UDM network element and carries third subscription context information indicating a unsubscribe requirement; and the UDM network element feeds back a deregistration request response message to the SMF network element based on the deregistration request message carrying the third subscription context information, carries the fourth subscription context information and identifies a unsubscribing result. It should be noted that, the process of sending the deregistration request message and receiving the deregistration request response message to the UDM network element by the AMF network element is the same as that of the SMF network element, and details are not described herein again.

In the embodiment, the unsubscribe step and the unregister step in the existing unregister process are combined, so that the unsubscribe function to the UDM network element is realized by carrying the subscription context information in the unregister related signaling.

Fifth embodiment:

in this embodiment, the service network element is an SMF network element, and the user data management network element is an UDM network element. As shown in fig. 7, in the session release flow, the SMF network element unsubscribes to the UDM network element, that is, the SMF network element sends a registration request message to the UDM network element, and carries third subscription context information indicating a unsubscribing requirement; and the UDM network element feeds back a deregistration request response message to the SMF network element based on the deregistration request message carrying the third subscription context information, carries the fourth subscription context information and identifies a unsubscribing result. Specifically, in the session release flow of this embodiment, the SMF network element no longer determines whether the current session meets the preset condition (for example, whether the current session is the last session in a session with a certain granularity), but the UDM network element determines whether the current session meets the preset condition after receiving the registration release request message, and when the current session meets the preset condition, identifies that the unsubscribe result is that unsubscribe is completed, and when the current session does not meet the preset condition, identifies that the unsubscribe result is that unsubscribe is not completed, thereby omitting the step of determining the current session by the SMF network element, and reducing the operating load of the SMF network element.

The embodiment combines the unsubscribe step and the unregister step in the existing session release process, so that the unsubscribe function to the UDM network element is realized by carrying the subscription context information in the unregister related signaling, and the signaling interaction quantity in the session release process is reduced.

In this way, the present embodiment completes the functions of subscription, update, unsubscribe, and the like by establishing the subscription context mechanism and carrying the subscription context information in other signaling, thereby omitting the subscription process and the unsubscribe process that the service network element specially initiates to the user data management network element, reducing the signaling number of the signaling flow, effectively reducing the time consumption of the flow, and reducing the operation load of the service network element. In addition, in the subscription removal process of the session release process, the process that the service network element judges whether the session is the last session under a certain granularity or whether a certain condition is met is omitted, so that the time consumption of the process is reduced, and the operation load of the service network element is reduced.

As shown in fig. 8, a block diagram of a subscription apparatus applied to a serving network element in an embodiment of the present invention is shown, where the apparatus includes:

a sending module 801, configured to send a first request message to a user data management network element, where the first request message is a registration request message or a subscription data request message, and the first request message carries first subscription context information to indicate a subscription requirement;

a receiving module 802, configured to receive a first response message fed back by the user data management network element based on the first request message, where the first response message is a registration request response message or a subscription data request response message, and the first response message carries second subscription context information to indicate a subscription result corresponding to the subscription requirement.

It should be noted that the apparatus provided in this embodiment can implement all the method steps that can be implemented by the method embodiment on the serving network element side, and can achieve the same technical effect, which is not described herein again.

As shown in fig. 9, a block diagram of a subscription apparatus applied to a user data management network element in an embodiment of the present invention is shown, where the apparatus includes:

a receiving module 901, configured to receive a first request message sent by a serving network element, where the first request message is a registration request message or a subscription data request message, and the first request message carries first subscription context information to indicate a subscription requirement;

a sending module 902, configured to feed back a first response message to the serving network element based on the first request message, where the first response message is a registration request response message or a subscription data request response message, and the first response message carries second subscription context information to indicate a subscription result corresponding to the subscription requirement.

It should be noted that the apparatus provided in this embodiment can implement all the method steps that can be implemented by the foregoing method embodiment on the user data management network element side, and can achieve the same technical effect, which is not described herein again.

Fig. 10 is a schematic structural diagram of a serving network element according to an embodiment of the present invention, and as shown in fig. 10, the serving network element 1000 may include at least one processor 1001, a memory 1002, at least one other user interface 1003, and a transceiver 1004. The various components in the serving network element 1000 are coupled together by a bus system 1005. It is understood that bus system 1005 is used to enable communications among the components connected. The bus system 1005 includes a power bus, a control bus, and a status signal bus, in addition to a data bus. For clarity of illustration, the various busses are labeled in fig. 10 as the bus system 1005, which may include any number of interconnected buses and bridges, with one or more processors, represented by the processor 1001, and various circuits, represented by the memory 1002, being linked together. The bus system may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, embodiments of the present invention will not be described any further. The bus interface provides an interface. The transceiver 1004 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium. The user interface 1003 may also be an interface capable of interfacing with a desired device for different user devices, including but not limited to a keypad, display, speaker, microphone, joystick, etc.

It is to be understood that the memory 1002 in embodiments of the present 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 PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of illustration and not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic random access memory (ddr Data Rate SDRAM, ddr SDRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 1002 of the described systems and methods for embodiments of the present invention is intended to comprise, without being limited to, these and any other suitable types of memory.

The processor 1001 is responsible for managing the bus system and general processing, and the memory 1002 may store computer programs or instructions used by the processor 1001 in performing operations, and in particular, the processor 1001 may be configured to:

sending a first request message to a user data management network element, wherein the first request message is a registration request message or a subscription data request message, and the first request message carries first subscription context information to indicate subscription requirements; and receiving a first response message fed back by the user data management network element based on the first request message, wherein the first response message is a registration request response message or a subscription data request response message, and the first response message carries second subscription context information to indicate a subscription result corresponding to the subscription requirement.

The method disclosed by the embodiment of the invention can be applied to the processor 1001 or can be implemented by the processor 1001. The processor 1001 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be implemented by integrated logic circuits of hardware or instructions in the form of software in the processor 1001. The Processor 1001 may be a general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, or discrete hardware components. The various methods, steps and logic blocks disclosed in the embodiments of the present invention may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 1002, and the processor 1001 reads the information in the memory 1002 and completes the steps of the method in combination with the hardware.

It is to be understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof. For a hardware implementation, the Processing units may be implemented within one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), general purpose processors, controllers, micro-controllers, microprocessors, other electronic units configured to perform the functions described herein, or a combination thereof.

For a software implementation, the techniques described may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described in connection with the embodiments of the invention. The software codes may be stored in a memory and executed by a processor. The memory may be implemented within the processor or external to the processor.

Optionally, as another embodiment, the processor 1001 is further configured to: when registering, the service network element is a mobility management network element, and sends a registration request message or a subscription data request message carrying the first subscription context information to the user data management network element; and/or, when a session is established, the service network element is a session management network element, and sends a subscription data request message carrying the first subscription context information to the user data management network element.

Optionally, as another embodiment, the processor 1001 is further configured to: when the serving network element is the mobility management network element, receiving the registration request response message fed back by the user data management network element based on the registration request message or the subscription data request response message fed back by the subscription data request message; and/or, when the service network element is a session management network element, receiving the subscription data request response message fed back by the user data management network element based on the subscription data request message.

Optionally, as another embodiment, the processor 1001 is further configured to: sending a second request message to the user data management network element, wherein the second request message is a de-registration request message, and the de-registration request message carries third subscription context information to indicate a de-subscription requirement; and receiving a second response message fed back by the user data management network element based on the second request message, wherein the second response message is a de-registration request response message and carries fourth subscription context information to indicate a de-subscription result corresponding to the de-subscription requirement, and the de-subscription result includes that de-subscription is completed or de-subscription is not completed.

Optionally, as another embodiment, when performing deregistration, the serving network element is a mobility management network element and a session management network element; when the session is released, the service network element is a session management network element, and when the user data management network element determines that the current session meets the preset condition, the unsubscribing result is that unsubscribing is completed, and when the user data management network element determines that the current session does not meet the preset condition, the unsubscribing result is that unsubscribing is not completed.

Optionally, as another embodiment, the processor 1001 is further configured to: sending a third request message to the user data management network element, wherein the third request message carries fifth subscription context information to indicate subscription update requirements; receiving a third response message fed back by the user data management network element based on the third request message, wherein the third response message carries sixth subscription context information to indicate a subscription update result corresponding to the subscription update requirement.

Optionally, as another embodiment, the processor 1001 is further configured to: sending a fourth request message to other service network elements, wherein the fourth request message carries seventh subscription context information to indicate subscription, unsubscribe or subscription update requirements; receiving a fourth response message fed back by the other service network elements based on the fourth request message, where the fourth response message carries eighth subscription context information to indicate a subscription, unsubscribe, or subscription update result corresponding to the subscription, unsubscribe, or subscription update requirement.

The service network element provided by the embodiment of the present invention can implement each process implemented by the service network element in the foregoing embodiments, and is not described herein again to avoid repetition.

Fig. 11 is a schematic structural diagram of a user data management network element according to an embodiment of the present invention, and as shown in fig. 11, the user data management network element 1100 may include at least one processor 1101, a memory 1102, at least one other user interface 1103, and a transceiver 1104. The various components in the user data management network element 1100 are coupled together by a bus system 1105. It is understood that the bus system 1105 is used to enable communications among the components. The bus system 1105 includes a power bus, a control bus, and a status signal bus in addition to a data bus. For clarity of illustration, however, the various busses are labeled in fig. 11 as the bus system 1105 which may include any number of interconnected buses and bridges, with one or more processors represented by the processor 1101 and the various circuits of memory represented by the memory 1102 being linked together. The bus system may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, embodiments of the present invention will not be described any further. The bus interface provides an interface. The transceiver 1104 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium. The user interface 1103 may also be an interface capable of interfacing with a desired device for different user devices, including but not limited to a keypad, display, speaker, microphone, joystick, etc.

It is to be understood that the memory 1102 in embodiments of the present invention can be either volatile memory or nonvolatile memory, or can 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 PROM (EEPROM), or a flash Memory. The volatile Memory may be a Random Access Memory (RAM) which serves as an external cache. By way of illustration and not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic random access memory (ddr Data Rate SDRAM, ddr SDRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 1102 of the subject systems and methods described in connection with the various embodiments of the invention is intended to comprise, without being limited to, these and any other suitable types of memory.

The processor 1101 is responsible for managing the bus system and general processing, and the memory 1102 may store computer programs or instructions used by the processor 1101 in performing operations, in particular, the processor 1101 may be configured to:

receiving a first request message sent by a service network element, wherein the first request message is a registration request message or a subscription data request message, and the first request message carries first subscription context information to indicate subscription requirements; and feeding back a first response message to the serving network element based on the first request message, wherein the first response message is a registration request response message or a subscription data request response message, and the first response message carries second subscription context information to indicate a subscription result corresponding to the subscription requirement.

The methods disclosed in the embodiments of the present invention described above may be implemented in the processor 1101 or by the processor 1101. The processor 1101 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by instructions in the form of hardware, integrated logic circuits, or software in the processor 1101. The Processor 1101 may be a general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component. The various methods, steps, and logic blocks disclosed in the embodiments of the present invention may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 1102, and the processor 1101 reads the information in the memory 1102 and completes the steps of the method in combination with the hardware thereof.

For a software implementation, the techniques described may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described in the embodiments of the invention. The software codes may be stored in a memory and executed by a processor. The memory may be implemented within the processor or external to the processor.

Optionally, as another embodiment, the processor 1101 is further configured to: receiving a registration request message or a subscription data request message which is sent by a mobility management network element and carries the first subscription context information when registering; and/or receiving a subscription data request message carrying the first subscription context information, which is sent by a session management network element when a session is established.

Optionally, as another embodiment, the processor 1101 is further configured to: feeding back the registration request response message to the mobility management network element based on the registration request message, or feeding back the subscription data request response message to the mobility management network element based on the subscription data request message; and/or feeding back the signing data request response message to the session management network element based on the signing data request message.

Optionally, as another embodiment, the processor 1101 is further configured to: receiving a second request message sent by the serving network element, wherein the second request message is a de-registration request message, and the de-registration request message carries third subscription context information to indicate a de-subscription requirement; feeding back a second response message to the serving network element based on the second request message, wherein the second response message is a de-registration request response message and carries fourth subscription context information to indicate a de-subscription result corresponding to the de-subscription requirement; the unsubscribe result comprises that the unsubscribe is completed or the unsubscribe is not completed.

Optionally, as another embodiment, when performing deregistration, the user data management network element is a mobility management network element and a session management network element; when the session is released, the user data management network element is a session management network element, when the user data management network element determines that the current session meets the preset condition, the unsubscribing result is that unsubscribing is completed, and when the user data management network element determines that the current session does not meet the preset condition, the unsubscribing result is that unsubscribing is not completed.

Optionally, as another embodiment, the processor 1101 is further configured to: receiving a third request message sent by the serving network element, where the third request message carries fifth subscription context information to indicate a subscription update requirement; feeding back a third response message to the serving network element based on the third request message, where the third response message carries sixth subscription context information to indicate a subscription update result corresponding to the subscription update requirement.

The user data management network element provided in the embodiment of the present invention can implement each process implemented by the user data management network element in the foregoing embodiments, and is not described herein again to avoid repetition.

The above description mainly introduces the solutions provided by the embodiments of the present invention from the perspective of electronic devices. It is understood that the electronic device provided by the embodiment of the present invention includes a hardware structure and/or a software module for performing the above functions. Those of skill in the art will readily appreciate that the present invention can be implemented in hardware or a combination of hardware and computer software for performing the exemplary elements and algorithm steps described in connection with the embodiments disclosed herein.

Whether a function is performed in hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. 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 invention.

In the embodiment of the present invention, the electronic device and the like may be divided into functional modules according to the above method examples, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode.

It should be noted that, the division of the modules in the embodiment of the present invention is schematic, and is only a logic function division, and there may be another division manner in actual implementation.

It will be clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be performed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to perform all or part of the above described functions. For the specific working processes of the system, the apparatus and the unit described above, reference may be made to the corresponding processes in the foregoing method embodiments, and details are not described here again.

In the embodiments provided in the present invention, it should be understood that the disclosed 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 modules or units is only one type of logical functional division, and other divisions may be realized in practice, for example, multiple 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.

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 invention 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 integrated unit may be implemented in the form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, all or part of the technical solution can 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) or a processor to execute all or part of the steps of the method according to the embodiments of the present invention. The computer storage medium is a non-transitory (English) medium, comprising: flash memory, removable hard drive, read only memory, random access memory, magnetic or optical disk, and the like.

On the other hand, embodiments of the present invention further provide a non-transitory computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the method steps provided in the foregoing embodiments, and can achieve the same technical effects, which are not described herein again.

Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.

Claims

1. A subscription method applied to a serving network element, comprising:

2. The subscription method of claim 1, wherein said sending a first request message to a user data management network element comprises:

when registering, the service network element is a mobility management network element, and sends a registration request message or a subscription data request message carrying the first subscription context information to the user data management network element; and/or the presence of a gas in the atmosphere,

and when session establishment is carried out, the service network element is a session management network element, and sends a subscription data request message carrying the first subscription context information to the user data management network element.

3. The subscription method according to claim 2, wherein said receiving a first response message fed back by the user data managing network element based on the first request message comprises:

when the service network element is the mobility management network element, receiving the registration request response message fed back by the user data management network element based on the registration request message or the subscription data request response message fed back based on the subscription data request message; and/or the presence of a gas in the atmosphere,

and when the service network element is a session management network element, receiving the subscription data request response message fed back by the user data management network element based on the subscription data request message.

4. The subscription method according to any one of claims 1 to 3, wherein after receiving the first response message fed back by the user data management network element based on the first request message, further comprising:

sending a second request message to the user data management network element, wherein the second request message is a de-registration request message, and the de-registration request message carries third subscription context information to indicate a de-subscription requirement;

Receiving a second response message fed back by the user data management network element based on the second request message, where the second response message is a de-registration request response message and carries fourth subscription context information to indicate a de-subscription result corresponding to the de-subscription requirement, and the de-subscription result includes that de-subscription is completed or de-subscription is not completed.

5. The subscription method as recited in claim 4,

when the registration is removed, the service network elements are a mobility management network element and a session management network element;

when the session is released, the service network element is a session management network element, and when the user data management network element determines that the current session meets the preset condition, the unsubscribing result is that unsubscribing is completed, and when the user data management network element determines that the current session does not meet the preset condition, the unsubscribing result is that unsubscribing is not completed.

6. The subscription method according to any one of claims 1 to 3, wherein after receiving the first response message fed back by the user data management network element based on the first request message, further comprising:

sending a third request message to the user data management network element, wherein the third request message carries fifth subscription context information to indicate subscription update requirements;

Receiving a third response message fed back by the user data management network element based on the third request message, wherein the third response message carries sixth subscription context information to indicate a subscription update result corresponding to the subscription update requirement.

7. The subscription method according to claim 1, further comprising:

sending a fourth request message to other service network elements, wherein the fourth request message carries seventh subscription context information to indicate subscription, unsubscribe or subscription update requirements;

receiving a fourth response message fed back by the other service network elements based on the fourth request message, wherein the fourth response message carries eighth subscription context information to indicate a subscription, unsubscribe, or subscription update result corresponding to the subscription, unsubscribe, or subscription update requirement.

8. A subscription method applied to a user data management network element is characterized by comprising the following steps:

receiving a first request message sent by a service network element, wherein the first request message is a registration request message or a subscription data request message, and the first request message carries first subscription context information to indicate subscription requirements;

9. The subscription method as claimed in claim 8, wherein said receiving the first request message sent by the serving network element includes:

receiving a registration request message or a subscription data request message which is sent by a mobility management network element and carries the first subscription context information when the registration is carried out; and/or the presence of a gas in the atmosphere,

and receiving a subscription data request message which is sent by a session management network element and carries the first subscription context information when the session is established.

10. The subscription method of claim 9, wherein the feeding back a first response message to the serving network element based on the first request message comprises:

feeding back the registration request response message to the mobility management network element based on the registration request message, or feeding back the subscription data request response message to the mobility management network element based on the subscription data request message; and/or the presence of a gas in the gas,

And feeding back the signing data request response message to the session management network element based on the signing data request message.

11. The subscription method according to any one of claims 8 to 10, wherein after feeding back a first response message to the serving network element based on the first request message, further comprising:

receiving a second request message sent by the serving network element, wherein the second request message is a de-registration request message, and the de-registration request message carries third subscription context information to indicate a de-subscription requirement;

feeding back a second response message to the serving network element based on the second request message, where the second response message is a deregistration request response message and carries fourth subscription context information to indicate a unsubscribe result corresponding to the unsubscribe requirement; the unsubscribe result comprises that the unsubscribe is completed or the unsubscribe is not completed.

12. The subscription method of claim 11,

13. The subscription method according to any one of claims 8 to 10, wherein after feeding back a first response message to the serving network element based on the first request message, further comprising:

receiving a third request message sent by the serving network element, where the third request message carries fifth subscription context information to indicate a subscription update requirement;

feeding back a third response message to the serving network element based on the third request message, where the third response message carries sixth subscription context information to indicate a subscription update result corresponding to the subscription update requirement.

14. A subscription apparatus, applied to a serving network element, comprising:

15. A subscription device applied to a user data management network element, comprising:

16. A serving network element comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the following steps when executing the computer program:

sending a first request message to a user data management network element, wherein the first request message is a registration request message or a subscription data request message and carries first subscription context information to indicate subscription requirements;

17. The serving network element of claim 16, wherein sending the first request message to the user data managing network element comprises:

and when the session is established, the service network element is a session management network element, and sends a subscription data request message carrying the first subscription context information to the user data management network element.

18. The serving network element of claim 17, wherein the receiving of the first response message fed back by the user data management network element based on the first request message comprises:

when the serving network element is the mobility management network element, receiving the registration request response message fed back by the user data management network element based on the registration request message or the subscription data request response message fed back by the subscription data request message; and/or the presence of a gas in the gas,

19. The serving network element of any one of claims 16 to 18, wherein, after receiving the first response message fed back by the user data management network element based on the first request message, the method further comprises:

and receiving a second response message fed back by the user data management network element based on the second request message, wherein the second response message is a de-registration request response message and carries fourth subscription context information to indicate a de-subscription result corresponding to the de-subscription requirement, and the de-subscription result includes that de-subscription is completed or de-subscription is not completed.

20. The serving network element of claim 19,

21. The serving network element according to any one of claims 16 to 18, wherein after receiving the first response message fed back by the user data managing network element based on the first request message, further comprising:

22. The serving network element of claim 16, further comprising:

Receiving a fourth response message fed back by the other service network elements based on the fourth request message, where the fourth response message carries eighth subscription context information to indicate a subscription, unsubscribe, or subscription update result corresponding to the subscription, unsubscribe, or subscription update requirement.

23. A user data managing network element comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor when executing the computer program performs the steps of:

24. The element according to claim 23, wherein the receiving the first request message sent by the serving element comprises:

Receiving a registration request message or a subscription data request message which is sent by a mobility management network element and carries the first subscription context information when registering; and/or the presence of a gas in the atmosphere,

and receiving a subscription data request message carrying the first subscription context information, which is sent by a session management network element when the session is established.

25. The element of claim 24, wherein the feeding back a first response message to the serving network element based on the first request message comprises:

26. The subscriber data managing network element according to any of claims 23 to 25, further comprising, after said feeding back a first response message to said serving network element based on said first request message:

Feeding back a second response message to the serving network element based on the second request message, wherein the second response message is a de-registration request response message and carries fourth subscription context information to indicate a de-subscription result corresponding to the de-subscription requirement; the unsubscribe result comprises that the unsubscribe is completed or the unsubscribe is not completed.

27. The user data managing network element of claim 26,

28. The subscriber data managing network element according to any of claims 23 to 25, further comprising, after said feeding back a first response message to said serving network element based on said first request message:

receiving a third request message sent by the serving network element, wherein the third request message carries fifth subscription context information to indicate subscription update requirements;

29. A non-transitory computer readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the subscription method according to any one of claims 1 to 7, or carries out the steps of the subscription method according to any one of claims 8 to 13.