Subscription and notification methods, and entities configured for implementing these methods

Abstract

A method for subscribing a first communicating entity to a second communicating entity. The method is implemented by the first entity and includes: transmitting a subscription request to the second communicating entity requesting subscription to notifications sent by the second communicating entity on at least one event monitored by the second communicating entity. The subscription request indicates at least one encoding format supported by the first communicating entity for receiving the notifications.

What is claimed is: 
     
         1 . A method for subscribing a first communicating entity with a second communicating entity, said method being implemented by the first communicating entity and comprising:
 transmitting a subscription request to the second communicating entity requesting subscription to notifications sent by the second communicating entity on at least one event monitored by the second communicating entity, wherein the subscription request indicates at least one encoding format supported by the first communicating entity for receiving the notifications.   
     
     
         2 . The method as claimed in  claim 1 , further comprising:
 following detection of one event corresponding to the subscription request, receiving, from the second communicating entity, a notification comprising information relating to said detected event that is encoded using one of the at least one encoding format supported by the first communicating entity and indicated in the subscription request.   
     
     
         3 . The method as claimed in  claim 1 , wherein at least one entity from among the first communicating entity and the second communicating entity is a network entity, an application function, or a user equipment. 
     
     
         4 . The method as claimed in  claim 1 , wherein at least one entity from among the first communicating entity and the second communicating entity is a network function or an instance of a network function. 
     
     
         5 . The method as claimed in  claim 1 , wherein the second communicating entity is a control entity managing a plurality of application entities of a network. 
     
     
         6 . The method as claimed in  claim 2 , wherein the detected event is a creation, a deletion or a modification of an element managed by the second communicating entity. 
     
     
         7 . The method as claimed in  claim 1 , wherein the notifications are compliant with a version of the Hypertext Transfer Protocol (HTTP) protocol. 
     
     
         8 . The method as claimed in  claim 1 , wherein at least one encoding format supported by the first communicating entity and indicated in the subscription request is a compression format. 
     
     
         9 . The method as claimed in  claim 2 , wherein the encoding format used to encode information relating to the detected event in the notification is a compression format. 
     
     
         10 . The method as claimed in  claim 1 , wherein, in the subscription request, the at least one encoding format supported by the first communicating entity is provided in a data structure comprising at least one communication option supported by the first communicating entity. 
     
     
         11 . The method according to  claim 1 , wherein the at least one encoding format is provided in a body of the subscription request. 
     
     
         12 . A method for notifying a first communicating entity of events, implemented by a second communicating entity, said method comprising:
 receiving a subscription request from the first communicating entity in order to receive notifications from the second communicating entity on at least one event monitored by the second communicating entity, wherein the subscription request indicates at least one encoding format supported by the first communicating entity for receiving the notifications.   
     
     
         13 . The method of  claim 12  further comprising:
 following detection by the second communicating entity of one of said events corresponding to the subscription request, sending the first communicating entity a notification comprising information relating to said detected event that is encoded using one of said encoding formats supported by the first communicating entity and indicated in the subscription request. 
 
     
     
         14 . The method as claimed in  claim 12 , wherein at least one entity from among the first communicating entity and the second communicating entity is a network entity, an application function, or a user equipment. 
     
     
         15 . The method as claimed in  claim 12 , wherein at least one entity from among the first communicating entity and the second communicating entity is a network function or an instance of a network function. 
     
     
         16 . The method as claimed in  claim 12 , wherein the second communicating entity is a control entity managing a plurality of application entities of a network. 
     
     
         17 . The method as claimed in  claim 12 , wherein the notifications are compliant with a version of the Hypertext Transfer Protocol (HTTP) protocol. 
     
     
         18 . The method as claimed in  claim 12 , wherein at least one encoding format supported by the first communicating entity and indicated in the subscription request is a compression format. 
     
     
         19 . A first communicating entity comprising:
 at least one processor; and   at least one non-transitory computer readable medium comprising instructions stored thereon which when executed by the at least one processor configure the first communicating entity to:   transmit a subscription request to a second communicating entity requesting subscription to notifications sent by the second communicating entity on at least one event monitored by the second communicating entity, wherein the subscription request indicates at least one encoding format supported by the first communicating entity for receiving the notifications.   
     
     
         20 . A second communicating entity comprising:
 at least one processor; and   at least one non-transitory computer readable medium comprising instructions stored thereon which when executed by the at least one processor configure the second communicating entity to:   receive a subscription request from a first communicating entity in order to receive notifications from the second communicating entity on at least one event monitored by the second communicating entity, wherein the subscription request indicates at least one encoding format supported by the first communicating entity for receiving the notifications.