Network nodes and methods therein for notification delivery
The present disclosure provides a method in a Network Function, NF, producer. The method includes transmitting, to a Service Communication Proxy, SCP, a notification request for delivering a notification. The notification request contains a Uniform Resource Identifier, URI, having a predetermined service path indicating that the notification request is associated with a default notification subscription.
1. A method in a Network Function, NF, producer, comprising:
transmitting, to a Service Communication Proxy, SCP, a notification request for delivering a notification, wherein the notification request contains a Uniform Resource Identifier, URI, having a predetermined service path indicating that the notification request is associated with a default notification subscription for which a callback URI is acquired to replace the URI as a target URI of the notification from the NF producer,
wherein the notification request further contains one or more parameters required for the SCP to select a target NF consumer of the notification; and wherein the one or more parameters comprise at least one of an N1 message class and an N2 information class for the notification.
2. A method in a network node implementing a Service Communication Proxy, SCP, function, comprising:
receiving, from a Network Function, NF, producer, a notification request for delivering a notification, wherein the notification request contains a Uniform Resource Identifier, URI, having a predetermined service path indicating that the notification request is associated with a default notification subscription for which a callback URI is acquired to replace the URI as a target URI of the notification from the NF producer;
selecting a target NF consumer of the notification based on the notification request;
acquiring the callback URI associated with the default notification subscription for the target NF consumer; and
transmitting the notification to the target NF consumer using the callback URI, wherein the notification request further contains one or more parameters required for the SCP to select the target NF consumer; and wherein the one or more parameters comprise at least one of an N1 message class and an N2 information class for the notification.
3. The method of claim 2 , wherein said selecting comprises performing a discovery towards an NF Repository Function, NRF, based on the one or more parameters, and said acquiring comprises acquiring the callback URI from an NF profile returned by the NRF.
4. A method in a Network Function, NF, producer, comprising:
transmitting, to a Service Communication Proxy, SCP, a notification request for delivering a notification to a default notification subscription for which a callback Uniform Resource Identifier, URI, is acquired to replace the URI as a target URI of the notification from the NF producer, wherein the notification request contains a Uniform Resource Identifier, URI, having a predetermined service path indicating that the notification request is associated with a default notification subscription, and the notification request indicates at least one of an N1 message class and an N2 information class for the notification.
5. The method of claim 4 , wherein the N1 message class or the N2 information class is carried in a header from which a query parameter for NF discovery is derivable.
6. A method in a network node implementing a Service Communication Proxy, SCP, function, comprising:
receiving, from a Network Function, NF, producer, a notification request for delivering a notification to a default notification subscription for which a callback Uniform Resource Identifier, URI, is acquired to replace the URI as a target URI of the notification from the NF producer, wherein the notification request contains a Uniform Resource Identifier, URI, having a predetermined service path indicating that the notification request is associated with a default notification subscription, and the notification request indicates at least one of an N1 message class and an N2 information class for the notification;
selecting or reselecting a target NF consumer of the notification based on the notification request; and
transmitting the notification to the target NF consumer.
7. The method of claim 6 , wherein the N1 message class or the N2 information class is carried in a header from which a query parameter for NF discovery is derivable.
8. The method of claim 6 , wherein said selecting or reselecting comprises performing a discovery towards an NF Repository Function, NRF, based on the N1 message class and/or the N2 information class.
9. A method in a Network Function, NF, consumer, comprising:
transmitting, to an NF Repository Function, NRF, an NF register request, wherein the NF register request contains a binding indication associated with the NF consumer for a default notification subscription for which a callback Uniform Resource Identifier, URI, is acquired to replace the URI as a target URI of the notification from the NF producer; or
transmitting, to an NF producer, a binding indication associated with the NF consumer for a default notification subscription in a service request that triggers delivering of a notification to the default notification subscription,
wherein the binding indication comprises one or more of:
a notification type,
an N1 message class,
an N2 information class, or
a scope associated with the default notification subscription.
10. The method of claim 9 , wherein the binding indication indicates a binding level set to an NF service instance, an NF service set, an NF instance, or an NF set; and/or wherein the binding indication is carried in a 3gpp-sbi-binding header or a 3gpp-sbi-routing-binding header.
11. A method in a Network Function, NF, producer, comprising:
acquiring a binding indication associated with an NF consumer for a default notification subscription for which a callback Uniform Resource Identifier, URI, is acquired to replace the URI as a target URI of the notification from the NF producer; and
transmitting, to a Service Communication Proxy, SCP, a notification request for delivering a notification to the default notification subscription, wherein the notification request contains the binding indication, and wherein the binding indication comprises one or more of:
a notification type,
an N1 message class,
an N2 information class, or
a scope associated with the default notification subscription.
12. The method of claim 11 , wherein said acquiring comprises:
acquiring the binding indication from an NF Repository Function, NRF, in an NF discovery process; or
acquiring the binding indication from the NF consumer in a service request that triggers the delivering of the notification to the default notification subscription.
13. The method of claim 11 , wherein the notification request further indicates one or more of:
a notification type,
an N1 message class,
an N2 information class, or
a scope associated with the default notification subscription.
14. The method of claim 13 , wherein at least one of the notification type, the N1 message class, the N2 information class, or the scope is carried in a header from which a query parameter for NF discovery is derivable.
15. The method of claim 11 , wherein the binding indication indicates a binding level set to an NF service instance, an NF service set, an NF instance, or an NF set; and/or wherein the binding indication is carried in a 3gpp-sbi-binding header or a 3gpp-sbi-routing-binding header.
16. A method in a network node implementing a Service Communication Proxy, SCP, function, comprising:
receiving, from a Network Function, NF, producer, a notification request for delivering a notification to a default notification subscription for which a callback Uniform Resource Identifier, URI, is acquired to replace the URI as a target URI of the notification from the NF producer;
acquiring a binding indication associated with an NF consumer for the default notification subscription; and
reselecting another NF consumer for delivering the notification to the default notification subscription based on the binding indication,
wherein the binding indication comprises one or more of:
a notification type,
an N1 message class,
an N2 information class, or
a scope associated with the default notification subscription.
17. The method of claim 16 , wherein said acquiring comprises:
acquiring the binding indication from an NF Repository Function, NRF, in an NF discovery process, or
extracting the binding indication from the notification request received from the NF producer.
18. The method of claim 16 , wherein the notification request further indicates one or more of:
a notification type,
an N1 message class,
an N2 information class, or
a scope associated with the default notification subscription.
19. The method of claim 18 , wherein at least one of the notification type, the N1 message class, the N2 information class, or the scope is carried in a header from which a query parameter for NF discovery is derivable.
20. The method of claim 16 , wherein said reselecting is in response to a failure, load balancing, or load rebalancing associated with the NF consumer.
21. The method of claim 16 , wherein the binding indication indicates a binding level set to an NF service instance, an NF service set, an NF instance, or an NF set; and/or wherein the binding indication is carried in a 3gpp-sbi-binding header or a 3gpp-sbi-routing-binding header.