Efficient handling of subscriptions

Patent metadata

Field	Value
Publication number	US-2022015023-A1
Application number	US-201917293876-A
Country	US
Kind code	A1
Filing date	Oct 17, 2019
Priority date	Nov 16, 2018
Publication date	Jan 13, 2022
Grant date	—

Abstract

Methods and nodes related to subscription handling and notifications, for instance, with respect to Network Function (NF) management services, are described.

First claim

1 - 41 . (canceled)

42 . A method in a second node, comprising:
receiving, from a first node, a first message, wherein said first message is a request for a subscription; sending, to said first node, a second message, wherein said second message comprises a subscription ID for the subscription; and receiving, from said first node, a third message, wherein said third message comprises a new subscription validity time for said subscription.

43 . The method of claim 42 , wherein said second message comprises an initial subscription validity time, further comprising:
accepting an extension of the subscription validity time and sending a fourth message in response to said third message, wherein said fourth message indicates an updated subscription validity time for said subscription.

44 . The method of claim 43 , wherein said updated subscription validity time for said subscription is different than the validity time period indicated by said new validity time.

45 . The method of claim 43 , wherein said fourth message is one or more of an HTTP 204 No Content message and an HTTP 200 OK message comprising subscription data.

46 . The method of claim 45 , wherein said subscription data comprises one or more of said updated time period, said subscription ID, and a subscription type.

47 . The method of claim 42 , further comprising:
receiving, from a third node, a fifth message, wherein said fifth message is a registration message; and sending, to said third node, a sixth message, wherein said sixth message indicates a registration status.

48 . The method of claim 42 , wherein said first message comprises input criteria, wherein said input criteria comprise one or more of an event type, an instance identifier corresponding to said second node, or a set of conditions identifying one or more network functions for said subscription.

49 . The method of claim 48 , wherein said first message is an HTTP POST message and said input criteria are in the form of a JSON document contained in the body of said HTTP POST message.

50 . The method of claim 48 ,
wherein said event type comprises one or more of register, de-register, or profile change, or wherein said set of conditions comprises one or of more network functions, NF, of a given type, all NFs supporting a given service, or all NFs belonging to a common set or group ID.

51 . The method of claim 47 , wherein said second node is a Network Repository Function, NRF, said first node is a NF Service Consumer, and said third node is a NF Service Producer.

52 . The method of claim 43 , further comprising:
generating said subscription ID; and determining said initial subscription validity time.

53 . The method of claim 42 , wherein said second message is an HTTP 201 message indicating that said first node has been successfully subscribed in accordance with said request for subscription.

54 . The method of claim 42 , wherein said third message is an HTTP PATCH message.

55 . The method of claim 42 , further comprising:
sending a fourth message in response to said third message, wherein said fourth message is an HTTP 400/500 message indicating one or more problems with a time extension request, and wherein said subscription is to receive notifications regarding updates to one or more services.

56 . A method in a first node, comprising:
sending to a second node, a first message, wherein said first message is a request for a subscription; receiving, from said second node, a second message, wherein said second message comprises a subscription ID for the subscription; and sending, to said second node, a third message, wherein said third message comprises a new validity time for said subscription.

57 . The method of claim 56 , wherein said second message comprises an initial subscription validity time, further comprising:
receiving a fourth message, wherein said fourth message indicates an updated validity time period for said subscription, wherein said updated validity time period for said subscription is different than the validity time indicated by said new validity time, or said fourth message is one or more of an HTTP 204 No Content message and an HTTP 200 message comprising subscription data, wherein said subscription data comprises one or more of said updated time period, said subscription ID, and a subscription type.

58 . The method of claim 56 , wherein said first message comprises input criteria, wherein said input criteria comprise one or more of an event type, an instance identifier corresponding to said second node, and a set of conditions identifying one or more network functions for said subscription, wherein
said first message is an HTTP POST message and said input criteria are in the form of a JSON document contained in the body said HTTP POST message, or said event type comprises one or more of register, de-register, and profile change, or said set of conditions comprises one or more of network functions, NF, of a given type, all NFs supporting a given service, or all NFs belonging to a common set or group ID.

59 . The method of claim 56 , wherein said second node is a Network Repository Function, NRF, said first node an NF Service Consumer, and said subscription relates to services provided by an NF Service Producer.

60 . The method of claim 56 , further comprising:
determining the new subscription validity time.

61 . The method of claim 56 , wherein said second message is an HTTP 201 message indicating successful subscription in accordance with said request for subscription, or said third message is an HTTP PATCH message, the method further comprising:
receiving a fourth message, wherein said fourth message is an HTTP 400/500 message indicating one or more problems with a time extension request, and wherein said subscription is to receive notifications regarding updates to one or more services.

Assignees

• Zhang Xiaowei
• Ericsson Telefon Ab L M

Inventors

• De-Gregorio-Rodriguez Jesus-Angel
• Zhang Xiaowei
• Ma Yubao
• Zhang xin yu

Classifications

• H04L67/02 Primary

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

• H04L67/51

  Discovery or management thereof, e.g. service location protocol [SLP] or web services · CPC title

• H04W48/18 Primary

  Selecting a network or a communication service · CPC title

• H04W4/50

  Service provisioning or reconfiguring · CPC title

• H04W8/18

  Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data · CPC title