Methods and Nodes for Notification Subscription

Abstract

The present disclosure provides a method (500) in a Network Function (NF) node for subscription to notification of data change in a Unified Data Management (UDM) node. The method (500) includes: transmitting (510) to the UDM node a request for retrieval of a user subscription data or a request for registration with the UDM node, the request for retrieval or the request for registration including a callback Uniform Resource Identifier (URI) for use by the UDM node to notify the NF node of the data change; and receiving (520) from the UDM node a response to the request for retrieval or the request for registration.

Claims

1.-20. (canceled)

21. A method in a Network Function, NF, node for subscription to notification of data change in a Unified Data Management, UDM, node, the method comprising: transmitting to the UDM node a request for retrieval of a user subscription data or a request for registration with the UDM node, the request for retrieval or the request for registration including a callback Uniform Resource Identifier, URI, for use by the UDM node to notify the NF node of the data change; and receiving from the UDM node a response to the request for retrieval or the request for registration.

22. The method of claim 21, wherein the request for retrieval comprises a query parameter, as a request for subscription to notification of the data change associated with the user subscription data, and wherein the callback URI is indicated in a key value of the query parameter.

23. The method of claim 22, wherein the request for retrieval is based on a Hyper Text Transfer Protocol, HTTP, GET or POST method.

24. The method of claim 21, wherein the request for registration comprises a request body, as a request for subscription to notification of the data change relevant to the NF node, and wherein the callback URI is carried in the request body.

25. The method of claim 24, wherein the request for registration is based on a Hyper Text Transfer Protocol, HTTP, PUT method.

26. The method of claim 21, wherein the response includes a subscription URI for a subscription created at the UDM.

27. The method of claim 26, further comprising: transmitting to the UDM node a request for unsubscription from the notification using the subscription URI.

28. The method of claim 21, wherein: the NF node is an Access and Mobility Management Function, AMF, node and the data change comprises a change in access and mobility subscription data, Session Management Function, SMF, selection subscription data, or Short Message Service, SMS, subscription data, the NF node is an SMF node and the data change comprises a change in session management subscription data, or the NF node is an SMS Function, SMSF, node and the data change comprises a change in SMS management subscription data.

29. A Network Function, NF, node for subscription to notification of data change in a Unified Data Management, UDM, node, the NF node comprising: a transceiver and a processor and a memory, the memory comprising instructions executable by the processor whereby the NF node is operative to: transmit to the UDM node a request for retrieval of a user subscription data or a request for registration with the UDM node, the request for retrieval or the request for registration including a callback Uniform Resource Identifier, URI, for use by the UDM node to notify the NF node of the data change; and receive from the UDM node a response to the request for retrieval or the request for registration.

30. A method in a Unified Data Management, UDM, node, for managing subscription of a Network Function, NF, node to notification of data change in the UDM node, comprising: receiving from the NF node a request for retrieval of a user subscription data or a request for registration with the UDM node, the request for retrieval or the request for registration including a callback Uniform Resource Identifier, URI, for use by the UDM node to notify the NF node of the data change; and creating a subscription to notification of the data change based on the callback URI.

31. The method of claim 30, wherein the request for retrieval comprises a query parameter, as a request for subscription to notification of the data change associated with the user subscription data, and wherein the callback URI is indicated in a key value of the query parameter.

32. The method of claim 31, wherein the request for retrieval is based on a Hyper Text Transfer Protocol, HTTP, GET or POST method.

33. The method of claim 30, wherein the request for registration comprises a request body, as a request for subscription to notification of the data change relevant to the NF node, and wherein the callback URI is carried in the request body.

34. The method of claim 33, wherein the request for registration is based on a Hyper Text Transfer Protocol, HTTP, PUT method.

35. The method of claim 30, further comprising: transmitting to the NF node a response to the request for retrieval or the request for registration, wherein the response includes a subscription URI for the created subscription.

36. The method of claim 35, further comprising: receiving from the NF node a request for unsubscription from the notification using the subscription URI; and removing the subscription in response to the request for unsubscription.

37. The method of claim 30, wherein: the NF node is an Access and Mobility Management Function, AMF, node and the data change comprises a change in access and mobility subscription data, Session Management Function, SMF, selection subscription data or Short Message Service, SMS, subscription data, the NF node is an SMF node and the data change comprises a change in session management subscription data, or the NF node is an SMS Function, SMSF, node and the data change comprises a change in SMS management subscription data.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0077] The above and other objects, features and advantages will be more apparent from the following description of embodiments with reference to the figures, in which:

[0078] FIG. 1 is a schematic diagram showing a service-based representation of the 5G architecture;

[0079] FIG. 2 is a schematic diagram showing a reference point representation of the 5G architecture;

[0080] FIG. 3 is a sequence diagram showing an explicit notification subscription procedure;

[0081] FIG. 4 is a sequence diagram showing a notification unsubscription procedure;

[0082] FIG. 5 is a flowchart illustrating a method in an NF node for subscription to notification of data change in a UDM node according to an embodiment of the present disclosure;

[0083] FIG. 6 is a flowchart illustrating a method in a UDM node for managing subscription of an NF node to notification of data change in the UDM node according to an embodiment of the present disclosure;

[0084] FIGS. 7A-7D are sequence diagrams each showing a notification subscription procedure according to an embodiment of the present disclosure;

[0085] FIGS. 8A-8C are sequence diagrams each showing a notification subscription procedure according to another embodiment of the present disclosure;

[0086] FIG. 9 is a block diagram of an NF node according to an embodiment of the present disclosure;

[0087] FIG. 10 is a block diagram of an NF node according to another embodiment of the present disclosure;

[0088] FIG. 11 is a block diagram of a UDM node according to an embodiment of the present disclosure; and

[0089] FIG. 12 is a block diagram of a UDM node according to another embodiment of the present disclosure.

DETAILED DESCRIPTION

[0090] References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0091] It shall be understood that although the terms “first” and “second” etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed terms. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be liming of example embodiments. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises”, “comprising”, “has”, “having”, “includes” and/or “including”, when used herein, specify the presence of stated features, elements, and/or components etc., but do not preclude the presence or addition of one or more other features, elements, components and or combinations thereof.

[0092] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

[0093] FIG. 5 is a flowchart illustrating a method 500 for subscription to notification of data change in a UDM node according to an embodiment of the present disclosure. The method 500 can be performed at an NF node, e.g., an AMF node, an SMF node or an SMSF node.

[0094] At block 510, a request for retrieval of a user subscription data or a request for registration with the UDM node is transmitted to the UDM node. The request for retrieval or the request for registration includes a callback URI for use by the UDM node to notify the NF node of the data change.

[0095] Here, the request for retrieval can include a query parameter, as a request for subscription to notification of the data change associated with the user subscription data. The callback URI can be indicated in a key value of the query parameter. The request for retrieval can be based on an HTTP GET or POST method.

[0096] The request for registration can include a request body, as a request for subscription to notification of the data change relevant to the NF node. The callback URI can be carried in the request body. The request for registration can be based on an HTTP PUT method.

[0097] As an example, the NF node can be an AMF node and the data change can include a change in access and mobility subscription data, SMF selection subscription data, or SMS subscription data. Alternatively, the NF node can be an SMF node and the data change can include a change in session management subscription data. Alternatively, the NF node can be a SMSF node and the data change can include a change in SMS management subscription data.

[0098] At block 520, a response to the request for retrieval or the request for registration is received from the UDM node.

[0099] In an example, the response can include a subscription URI for a subscription created at the UDM. The NF node can transmit to the UDM node a request for unsubscription from the notification using the subscription URI.

[0100] FIG. 6 is a flowchart illustrating a method 600 for managing subscription of an NF node to notification of data change in the UDM node according to an embodiment of the present disclosure. The method 600 can be performed at a UDM node.

[0101] At block 610, a request for retrieval of a user subscription data or a request for registration with the UDM node is received from the NF node. The request for retrieval or the request for registration includes a callback URI for use by the UDM node to notify the NF node of the data change.

[0102] Here, the request for retrieval can include a query parameter, as a request for subscription to notification of the data change associated with the user subscription data. The callback URI can be indicated in a key value of the query parameter. The request for retrieval can be based on an HTTP GET or POST method.

[0103] The request for registration can include a request body, as a request for subscription to notification of the data change relevant to the NF node. The callback URI can be carried in the request body. The request for registration can be based on an HTTP PUT method.

[0104] As an example, the NF node can be an AMF node and the data change can include a change in access and mobility subscription data, SMF selection subscription data, or SMS subscription data. Alternatively, the NF node can be an SMF node and the data change can include a change in session management subscription data. Alternatively, the NF node can be a SMSF node and the data change can include a change in SMS management subscription data.

[0105] At block 620, a subscription to notification of the data change is created based on the callback URI.

[0106] In an example, the UDM node can transmit to the NF node a response to the request for retrieval or the request for registration. The response can include a subscription URI for the created subscription.

[0107] In an example, the UDM node can receive from the NF node a request for unsubscription from the notification using the subscription URI. Then, the UDM node can remove the subscription in response to the request for unsubscription.

[0108] In the following, the above methods 500 and 600 will be explained in further detail with reference to FIGS. 7A-7D and 8A-8C.

[0109] FIGS. 7A-7D are sequence diagrams each showing a notification subscription procedure using a request for retrieval according to an embodiment of the present disclosure.

[0110] In particular, as shown in FIG. 7A, at 711, an AMF node sends to the UDM node an HTTP GET request for retrieval of a UE's access and mobility subscription data from the UDM node. The GET request can have a URI, or Uniform Resource Locator (URL), such as: [0111] http://{apiRoot}/nudm-sdm/v1/{supi}/am-data?notify={callbackURI}.

[0112] Here, a query parameter “notify={callbackURI}” is included in the request and its presence indicates that the AMF node is requesting for subscription to notification of changes in the access and mobility subscription data. The key value of the parameter indicates a callback URI for use by the UDM node to notify such changes.

[0113] At 712, the UDM node responds with “200 OK”, having a message body containing the requested access and mobility subscription data along with a subscription URI for the subscription created at the UDM node. Then, the AMF node can save the subscription URI, which can be used later for explicit unsubscription from the notification as described above in connection with FIG. 4.

[0114] On the other hand, an HTTP GET request without the query parameter means that no request for subscription is made. For the subscription created at the UDM in response to the GET request at 711, a later HTTP GET request for retrieval of the UE's access and mobility subscription data without the query parameter may indicate to the UDM node that the AMF node now intends to unsubscribe from the notification and the UDM node can remove the created subscription in response to the absence of the query parameter. However, such absence of the query parameter may not result in removal of a subscription created in response to the explicit subscription request as shown in FIG. 3, as the latter has a higher priority.

[0115] As shown in FIG. 7B, at 721, an AMF node sends to the UDM node an HTTP GET request for retrieval of a UE's SMF selection subscription data from the UDM node. The GET request can have a URI or URL such as: [0116] http://{apiRoot}/nudm-sdm/v1/{supi}/smf-select-data?notify={callbackURI}.

[0117] Here, a query parameter “notify={callbackURI}” is included in the request and its presence indicates that the AMF node is requesting for subscription to notification of changes in the SMF selection subscription data. The key value of the parameter indicates a callback URI for use by the UDM node to notify such changes.

[0118] At 722, the UDM node responds with “200 OK”, having a message body containing the requested SMF selection subscription data along with a subscription URI for the subscription created at the UDM node. Then, the AMF node can save the subscription URI, which can be used later for explicit unsubscription from the notification as described above in connection with FIG. 4.

[0119] As described above, a later HTTP GET request for retrieval of the SMF selection subscription data without the query parameter may result in removal of the subscription created at the UDM node in response to the GET request at 721, but not a subscription created in response to the explicit subscription request as shown in FIG. 3.

[0120] The above sequences described in FIGS. 7A and 7B also apply when the AMF node subscribes to notification of changes in SMS subscription data and further details thereof will be omitted here.

[0121] As shown in FIG. 7C, at 731, an SMF node sends to the UDM node an HTTP GET request for retrieval of an UE's session management subscription data from the UDM node. The GET request can have a URI or URL such as: [0122] http://{apiRoot}/nudm-sdm/v1/{supi}/sm-data?notify={callbackURI}.

[0123] Here, a query parameter “notify={callbackURI}” is included in the request and its presence indicates that the SMF node is requesting for subscription to notification of changes in the session management subscription data. The key value of the parameter indicates a callback URI for use by the UDM node to notify such changes.

[0124] At 732, the UDM node responds with “200 OK”, having a message body containing the requested session management subscription data along with a subscription URI for the subscription created at the UDM node. Then, the SMF node can save the subscription URI, which can be used later for explicit unsubscription from the notification as described above in connection with FIG. 4.

[0125] As described above, a later HTTP GET request for retrieval of the session management subscription data without the query parameter may result in removal of the subscription created at the UDM node in response to the GET request at 731, but not a subscription created in response to the explicit subscription request as shown in FIG. 3.

[0126] As shown in FIG. 7D, at 741, an SMSF node sends to the UDM node an HTTP GET request for retrieval of a UE's SMS management subscription data from the UDM node. The GET request can have a URI or URL such as: [0127] http://{apiRoot}/nudm-sdm/v1/{supi}/sms-data?notify={callbackURI}.

[0128] Here, a query parameter “notify={callbackURI}” is included in the request and its presence indicates that the SMSF node is requesting for subscription to notification of changes in the SMS management subscription data. The key value of the parameter indicates a callback URI for use by the UDM node to notify such changes.

[0129] At 742, the UDM node responds with “200 OK”, having a message body containing the requested SMS management subscription data along with a subscription URI for the subscription created at the UDM node. Then, the SMSF node can save the subscription URI, which can be used later for explicit unsubscription from the notification as described above in connection with FIG. 4.

[0130] As described above, a later HTTP GET request for retrieval of the SMS management subscription data without the query parameter may result in removal of the subscription created at the UDM node in response to the GET request at 741, but not a subscription created in response to the explicit subscription request as shown in FIG. 3.

[0131] It is to be noted that, in FIGS. 7A-7D, as an alternative to the HTTP GET method, an HTTP POST method can be used for each request for retrieval.

[0132] FIGS. 8A-8C are sequence diagrams each showing a notification subscription procedure using a request for registration according to an embodiment of the present disclosure.

[0133] In particular, as shown in FIG. 8A, at 811, an AMF node sends to the UDM node an HTTP PUT request for a UE's 3GPP access and mobility registration with the UDM node. The PUT request can have a URI or URL such as: [0134] http://{apiRoot}/nudm-sdm/v1/{ue-id}/registrations/amf-3gpp-access.

[0135] A request body can be included in the request and its presence indicates that the AMF node is requesting for subscription to notification of changes in data relevant to the AMF node, e.g., access and mobility subscription data, SMF selection subscription data and/or SMS subscription data. The request body carries a callback URI for use by the UDM node to notify such changes.

[0136] At 812, the UDM node responds with “201 Created”, having a message body containing a 3GPP access and mobility registration result along with a subscription URI for the subscription created at the UDM node. Then, the AMF node can save the subscription URI, which can be used later for explicit unsubscription from the notification as described above in connection with FIG. 4.

[0137] Alternatively or additionally, at 813, the AMF node sends to the UDM node an HTTP PUT request for a UE's non-3GPP access and mobility registration with the UDM node. The PUT request can have a URI or URL such as: [0138] http://{apiRoot}/nudm-sdm/v1/{ue-id}/registrations/amf-non-3gpp-access.

[0139] A request body can be included in the request and its presence indicates that the AMF node is requesting for subscription to notification of changes in data relevant to the AMF node, e.g., access and mobility subscription data, SMF selection subscription data and/or SMS subscription data. The request body carries a callback URI for use by the UDM node to notify such changes.

[0140] At 814, the UDM node responds with “201 Created”, having a message body containing a non-3GPP access and mobility registration result along with a subscription URI for the subscription created at the UDM node. Then, the AMF node can save the subscription URI, which can be used later for explicit unsubscription from the notification as described above in connection with FIG. 4.

[0141] As shown in FIG. 8B, at 821, an SMF node sends to the UDM node an HTTP PUT request for a UE's session management registration with the UDM node. The PUT request can have a URI or URL such as: [0142] http://{apiRoot}/nudm-sdm/v1/{ue-id}/registrations/smf-registrations/{pduSessionId}.

[0143] A request body can be included in the request and its presence indicates that the SMF node is requesting for subscription to notification of changes in data relevant to the SMF node, e.g., session management subscription data. The request body carries a callback URI for use by the UDM node to notify such changes.

[0144] At 822, the UDM node responds with “201 Created”, having a message body containing a registration result along with a subscription URI for the subscription created at the UDM node. Then, the SMF node can save the subscription URI, which can be used later for explicit unsubscription from the notification as described above in connection with FIG. 4.

[0145] As shown in FIG. 8C, at 831, an SMSF node sends to the UDM node an HTTP PUT request for a UE's SMSF 3GPP access registration with the UDM node. The PUT request can have a URI or URL such as: [0146] http://{apiRoot}/nudm-sdm/v1/{ue-id}/registrations/smsf-3gpp-access.

[0147] A request body can be included in the request and its presence indicates that the SMSF node is requesting for subscription to notification of changes in data relevant to the SMSF node, e.g., SMS management subscription data. The request body carries a callback URI for use by the UDM node to notify such changes.

[0148] At 832, the UDM node responds with “201 Created”, having a message body containing an SMSF 3GPP access registration result along with a subscription URI for the subscription created at the UDM node. Then, the SMSF node can save the subscription URI, which can be used later for explicit unsubscription from the notification as described above in connection with FIG. 4.

[0149] Alternatively or additionally, at 833, the SMSF node sends to the UDM node an HTTP PUT request for a UE's SMSF non-3GPP access registration with the UDM node. The PUT request can have a URI or URL such as: [0150] http://{apiRoot}/nudm-sdm/v1/{ue-id}/registrations/smsf-non-3gpp-access.

[0151] A request body can be included in the request and its presence indicates that the SMSF node is requesting for subscription to notification of changes in data relevant to the SMSF node, e.g., SMS management subscription data. The request body carries a callback URI for use by the UDM node to notify such changes.

[0152] At 834, the UDM node responds with “201 Created”, having a message body containing an SMSF non-3GPP access registration result along with a subscription URI for the subscription created at the UDM node. Then, the SMSF node can save the subscription URI, which can be used later for explicit unsubscription from the notification as described above in connection with FIG. 4.

[0153] It is to be noted that, in FIGS. 8A-8C, as an alternative to the “201 Created” response, a “200 OK” or “204 No Content” response can be used.

[0154] Correspondingly to the method 500 as described above, an NF node is provided. FIG. 9 is a block diagram of a NF node 900 according to an embodiment of the present disclosure. The NF node 900 can subscribe to notification of data change in a UDM node.

[0155] As shown in FIG. 9, the NF node 900 includes a transmitting unit 910 configured to transmit to the UDM node a request for retrieval of a user subscription data or a request for registration with the UDM node. The request for retrieval or the request for registration includes a callback URI for use by the UDM node to notify the NF node of the data change. The NF node 900 further includes a receiving unit 920 configured to receive from the UDM node a response to the request for retrieval or the request for registration.

[0156] In an embodiment, the request for retrieval can include a query parameter, as a request for subscription to notification of the data change associated with the user subscription data, and the callback URI can be indicated in a key value of the query parameter.

[0157] In an embodiment, the request for retrieval can be based on an HTTP GET or POST method.

[0158] In an embodiment, the request for registration can include a request body, as a request for subscription to notification of the data change relevant to the NF node, and the callback URI can be carried in the request body.

[0159] In an embodiment, the request for registration can be based on an HTTP PUT method.

[0160] In an embodiment, the response can include a subscription URI for a subscription created at the UDM.

[0161] In an embodiment, the transmitting unit 910 can further be configured to transmit to the UDM node a request for unsubscription from the notification using the subscription URI.

[0162] In an embodiment, the NF node can be an AMF node and the data change can include a change in access and mobility subscription data, SMF selection subscription data, or SMS subscription data. Alternatively, the NF node can be an SMF node and the data change can include a change in session management subscription data. Alternatively, the NF node can be a SMSF node and the data change can include a change in SMS management subscription data.

[0163] The transmitting unit 910 and the receiving unit 920 can be implemented as a pure hardware solution or as a combination of software and hardware, e.g., by one or more of: a processor or a micro-processor and adequate software and memory for storing of the software, a Programmable Logic Device (PLD) or other electronic component(s) or processing circuitry configured to perform the actions described above, and illustrated, e.g., in FIG. 5.

[0164] FIG. 10 is a block diagram of an NF node 1000 according to another embodiment of the present disclosure. The NF node 1000 can subscribe to notification of data change in a UDM node.

[0165] The NF node 1000 includes a transceiver 1010, a processor 1020 and a memory 1030. The memory 1030 contains instructions executable by the processor 1020 whereby the NF node 1000 is operative to perform the actions, e.g., of the procedure described earlier in conjunction with FIG. 5. Particularly, the memory 1030 contains instructions executable by the processor 1020 whereby the NF node 1000 is operative to: transmit to the UDM node a request for retrieval of a user subscription data or a request for registration with the UDM node, the request for retrieval or the request for registration including a callback URI for use by the UDM node to notify the NF node of the data change; and receive from the UDM node a response to the request for retrieval or the request for registration.

[0166] In an embodiment, the request for retrieval can include a query parameter, as a request for subscription to notification of the data change associated with the user subscription data, and the callback URI can be indicated in a key value of the query parameter.

[0167] In an embodiment, the request for retrieval can be based on an HTTP GET or POST method.

[0168] In an embodiment, the request for registration can include a request body, as a request for subscription to notification of the data change relevant to the NF node, and the callback URI can be carried in the request body.

[0169] In an embodiment, the request for registration can be based on an HTTP PUT method.

[0170] In an embodiment, the response can include a subscription URI for a subscription created at the UDM.

[0171] In an embodiment, the memory 1030 can further contain instructions executable by the processor 1020 whereby the NF node 1000 is operative to: transmit to the UDM node a request for unsubscription from the notification using the subscription URI.

[0172] In an embodiment, the NF node can be an AMF node and the data change can include a change in access and mobility subscription data, SMF selection subscription data, or SMS subscription data. Alternatively, the NF node can be an SMF node and the data change can include a change in session management subscription data. Alternatively, the NF node can be a SMSF node and the data change can include a change in SMS management subscription data.

[0173] Correspondingly to the method 600 as described above, a UDM node is provided. FIG. 11 is a block diagram of a UDM node 1100 according to an embodiment of the present disclosure. The UDM node 1100 can manage subscription of an NF node to notification of data change in the UDM node.

[0174] As shown in FIG. 11, the UDM node 1100 includes a receiving unit 1110 configured to receive from the NF node a request for retrieval of a user subscription data or a request for registration with the UDM node. The request for retrieval or the request for registration includes a callback URI for use by the UDM node to notify the NF node of the data change. The UDM node 1100 further includes a subscription managing unit 1120 configured to create a subscription to notification of the data change based on the callback URI.

[0175] In an embodiment, the request for retrieval can include a query parameter, as a request for subscription to notification of the data change associated with the user subscription data, and the callback URI can be indicated in a key value of the query parameter.

[0176] In an embodiment, the request for retrieval can be based on an HTTP GET or POST method.

[0177] In an embodiment, the request for registration can include a request body, as a request for subscription to notification of the data change relevant to the NF node, and the callback URI can be carried in the request body.

[0178] In an embodiment, the request for registration can be based on an HTTP PUT method.

[0179] In an embodiment, the UDM node 1100 can further include a transmitting unit configured to transmit to the NF node a response to the request for retrieval or the request for registration. The response can include a subscription URI for the created subscription.

[0180] In an embodiment, the receiving unit 1110 can further be configured to receive from the NF node a request for unsubscription from the notification using the subscription URI. The subscription managing unit 1120 can further be configured to remove the subscription in response to the request for unsubscription.

[0181] In an embodiment, the NF node can be an AMF node and the data change can include a change in access and mobility subscription data, SMF selection subscription data, or SMS subscription data. Alternatively, the NF node can be an SMF node and the data change can include a change in session management subscription data. Alternatively, the NF node can be a SMSF node and the data change can include a change in SMS management subscription data.

[0182] The receiving unit 1110 and the subscription managing unit 1120 can be implemented as a pure hardware solution or as a combination of software and hardware, e.g., by one or more of: a processor or a micro-processor and adequate software and memory for storing of the software, a Programmable Logic Device (PLD) or other electronic component(s) or processing circuitry configured to perform the actions described above, and illustrated, e.g., in FIG. 6.

[0183] FIG. 12 is a block diagram of a UDM node 1200 according to another embodiment of the present disclosure. The UDM node 1200 can manage subscription of an NF node to notification of data change in the UDM node.

[0184] The UDM node 1200 includes a transceiver 1210, a processor 1220 and a memory 1230. The memory 1230 contains instructions executable by the processor 1220 whereby the UDM node 1200 is operative to perform the actions, e.g., of the procedure described earlier in conjunction with FIG. 6. Particularly, the memory 1230 contains instructions executable by the processor 1220 whereby the UDM node 1200 is operative to: receive from the NF node a request for retrieval of a user subscription data or a request for registration with the UDM node, the request for retrieval or the request for registration including a callback URI for use by the UDM node to notify the NF node of the data change; and create a subscription to notification of the data change based on the callback URI.

[0185] In an embodiment, the request for retrieval can include a query parameter, as a request for subscription to notification of the data change associated with the user subscription data, and the callback URI can be indicated in a key value of the query parameter.

[0186] In an embodiment, the request for retrieval can be based on an HTTP GET or POST method.

[0187] In an embodiment, the request for registration can include a request body, as a request for subscription to notification of the data change relevant to the NF node, and the callback URI can be carried in the request body.

[0188] In an embodiment, the request for registration can be based on an HTTP PUT method.

[0189] In an embodiment, the memory 1230 can further contain instructions executable by the processor 1220 whereby the UDM node 1200 is operative to: transmit to the NF node a response to the request for retrieval or the request for registration. The response can include a subscription URI for the created subscription.

[0190] In an embodiment, the memory 1230 can further contain instructions executable by the processor 1220 whereby the UDM node 1200 is operative to: receive from the NF node a request for unsubscription from the notification using the subscription URI; and remove the subscription in response to the request for unsubscription.

[0191] In an embodiment, the NF node can be an AMF node and the data change can include a change in access and mobility subscription data, SMF selection subscription data, or SMS subscription data. Alternatively, the NF node can be an SMF node and the data change can include a change in session management subscription data. Alternatively, the NF node can be a SMSF node and the data change can include a change in SMS management subscription data.

[0192] The present disclosure also provides at least one computer program product in the form of a non-volatile or volatile memory, e.g., a non-transitory computer readable storage medium, an Electrically Erasable Programmable Read-Only Memory (EEPROM), a flash memory and a hard drive. The computer program product includes a computer program. The computer program includes: code/computer readable instructions, which when executed by the processor 1020 causes the NF node 1000 to perform the actions, e.g., of the procedure described earlier in conjunction with FIG. 5; or code/computer readable instructions, which when executed by the processor 1220 causes the UDM node 1200 to perform the actions, e.g., of the procedure described earlier in conjunction with FIG. 6.

[0193] The computer program product may be configured as a computer program code structured in computer program modules. The computer program modules could essentially perform the actions of the flow illustrated in FIG. 5 or 6.

[0194] The processor may be a single CPU (Central processing unit), but could also comprise two or more processing units. For example, the processor may include general purpose microprocessors; instruction set processors and/or related chips sets and/or special purpose microprocessors such as Application Specific Integrated Circuit (ASICs). The processor may also comprise board memory for caching purposes. The computer program may be carried by a computer program product connected to the processor. The computer program product may comprise a non-transitory computer readable storage medium on which the computer program is stored. For example, the computer program product may be a flash memory, a Random-access memory (RAM), a Read-Only Memory (ROM), or an EEPROM, and the computer program modules described above could in alternative embodiments be distributed on different computer program products in the form of memories.

[0195] The disclosure has been described above with reference to embodiments thereof. It should be understood that various modifications, alternations and additions can be made by those skilled in the art without departing from the spirits and scope of the disclosure. Therefore, the scope of the disclosure is not limited to the above particular embodiments but only defined by the claims as attached.