Systems and methods to update the active notification channel in service enabler architecture layer (SEAL) notification management service

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Embodiments herein disclose a method for managing an active notification channel in a SEAL notification management service in a wireless network by a notification management client.

Description

SYSTEMS AND METHODS TO UPDATE THE ACTIVE NOTIFICATION CHANNEL IN SERVICE ENABLER ARCHITECTURE LAYER (SEAL) NOTIFICATION MANAGEMENT SERVICE

[0001] Embodiments disclosed herein relate to wireless communication networks, and more particularly to Service Enabler Architecture Layer (SEAL) Notification Management services in the wireless communication networks.

[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in "Sub 6GHz" bands such as 3.5GHz, but also in "Above 6GHz" bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

[0008] As of date, each applications (e.g., chat application, social networking application or the like) on a User Equipment (UE) (e.g., smartphone, laptop or the like) listens for notification messages from their respective servers called as Vertical Application Layer (VAL) servers. This creates more traffic on a network side, since each VAL servers are deployed in different regions running on internet protocol (IP) address and ports which is obvious to be different. Due to continuous listening from the UE for the notifications, the process leads in consuming more computing resources and power on the UE.

[0009] A SEAL Notification Management service proposed in Third Generation Partnership Project　(3GPP) technical specification (TS) 23.434 defines a notification mechanism to be consumed by the application mentioned above. A SEAL Notification Management Client (SNM-C) sends a create notification channel request to a SEAL Notification Management Server (SNM-S) and in case of successful processing the SNM-S shall send response with callback associated with the SNM-S.

[0010] Currently, the specification defines procedures to provide a notification channel with an associated callback between the SNM-S and the SNM-C along with validity duration of the notification channel as part of response, when the SNM-C creates the notification channel with the SNM-S. The applications on the UE can use this notification channel by sharing the callback to their VAL servers for pushing future notification messages through the SNM-S. Thus SEAL Notification Management offloads the responsibility of notification management performed by each such application on the UE and realizes same with simplified approach with just few (or one) notification channel between the SNM-C and the SNM-S.

[0011] The notification management service proposed in the 3GPP TS 23.434 has not defined any procedures to UPDATE a "validity duration" of the active notification channel between the SNM-C and the SNM-S resulting in closure of the notification channel from the notification management server on reaching the expiry time. This results in performing the creation of notification channel procedure again and this creation procedure keeps repeating each time the active channel expires until the services continue consuming notification channel. This shall introduce latency in all services that are consuming notification channel when repeating the creation notification channel procedure and shall delay delivering notification messages to services further delay in notifying messages to end user that finally hampers Quality of Experience (QoE).

[0012] In other word, 3GPP TS 23.434 for notification management, does not provide any methods to update the attribute associated with active notification channel. This lead to the notification management client not being able to update the new expiry timer for the active notification channel resulting in closure of the notification channel from the notification management server.

[0013] The above information is presented as background information only to help the reader to understand the present invention. Applicants have made no determination and make no assertion as to whether any of the above might be applicable as prior art with regard to the present application.

[0014] The principal object of the embodiments herein is to disclose systems and methods for updating the active notification channel in SEAL Notification Management service, wherein the notification management client is allowed to share an expiry timer as part of a proposed update procedure to the notification management server.

[0015] Accordingly, the embodiments herein provide a method for managing an active notification channel in a SEAL notification management service in a wireless network. The method includes detecting, by a notification management client, an expiry timer of the active notification channel being approached and a need for updating a new expiry time associated with the active notification channel with a notification management server. The new expiry time indicates a proposed validity duration for the active notification channel. Further, the method includes sending, by the notification management client, an update notification channel request to the notification management server based on the detection. Further, the method includes receiving, by the notification management client, an update notification channel response including the expiry time for the active notification channel upon validating the valid duration for the active notification channel at the notification management server. Further, the method includes storing, by the notification management client, the new expiry time of the notification management channel at the notification management client.

[0016] In an embodiment, the update notification channel request includes a requestor identity, a channel identifier (ID) and the validity duration.

[0017] In an embodiment, the requestor identity represents identity of the notification management client. The channel ID identifies the notification channel to be updated. The validity duration proposes the expiry time that indicates a time duration the notification channel will be active as requested by the SEAL notification management client and acknowledged by the notification management server.

[0018] In an embodiment, the update notification channel response includes a result indicating if updating of the active notification channel is success or failure.

[0019] Accordingly, the embodiments herein provide a method for managing an active notification channel in a SEAL notification management service in a wireless network. The method includes receiving, by a notification management server, an update notification channel request from a notification management client, when the notification management client detects an expiry timer of the active notification channel being approached and a need for updating a new expiry time associated with the active notification channel with the notification management server. The new expiry time indicates a proposed validity duration for the active notification channel. Further, the method includes authenticating, by the notification management server, the notification management client. Further, the method includes authorizing, by the notification management server, the update notification channel request. Further, the method includes sending, by the notification management server, an update notification channel response including the expiry time for the active notification channel in the proposed "Validity Duration" attribute, to the notification management client based on the update notification channel request.

[0020] Accordingly, the embodiments herein provide a notification management client including a SEAL notification management service controller coupled with a processor and a memory. The SEAL notification management service controller isconfigured to detect an expiry timer of the active notification channel being approached and a need for updating a new expiry time associated with the active notification channel with a notification management server. The new expiry time indicates a proposed validity duration for the active notification channel. Further, the SEAL notification management service controller is configured to send an update notification channel request to the notification management server based on the detection. Further, the SEAL notification management service controller is configured to receive an update notification channel response including the expiry time for the active notification channel upon validating the valid duration for the active notification channel at the notification management server. Further, the SEAL notification management service controller is configured to store by the expiry time of the notification management channel at the notification management client.

[0021] Accordingly, the embodiments herein provide a notification management server including a SEAL notification management service controller coupled with a processor and a memory. The SEAL notification management service controller is configured to receive an update notification channel request from a notification management client, when the notification management client detects an expiry timer of the active notification channel being approached and a need for updating a new expiry time associated with the active notification channel with the notification management server. The new expiry time indicates a proposed validity duration for the active notification channel. Further, the SEAL notification management service controller is configured to authenticate the notification management client. Further, the SEAL notification management service controller is configured to authorize the update notification channel request. Further, the SEAL notification management service controller is configured to send an update notification channel response including the valid duration with the expiry time value as shared by notification management client or a newly proposed expiry time from notification management server based on a local policy for the active notification channel to the notification management client in reply to the update notification channel request.

[0022] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating at least one embodiment and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.

[0023] According to an embodiment of present disclosure, the notification management client and the notification management server　can　efficiently　perform　a　communication.

[0024] The embodiments disclosed herein are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:

[0025] FIG. 1 illustrates a new procedure for updating active notification channel sent from a notification management client to a notification management server in a wireless network, according to embodiments as disclosed herein.

[0026] FIG. 2 illustrates various hardware components of the notification management client, according to the embodiments as disclosed herein.

[0027] FIG. 3 illustrates various hardware components of a notification management server, according to the embodiments as disclosed herein.

[0028] FIG. 4 illustrates a flow chart illustrating a method, implemented by the notification management client, for managing an active notification channel in a SEAL notification management service in the wireless network, according to the embodiments as disclosed herein.

[0029] FIG. 5 illustrates a flow chart illustrating a method, implemented by the notification management server, for managing an active notification channel in the SEAL notification management service in the wireless network, according to the embodiments as disclosed herein.

[0030] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0031] For the purposes of interpreting this specification, the definitions (as defined herein) will apply and whenever appropriate the terms used in singular will also include the plural and vice versa. It is to be understood that the terminology used herein is for the purposes of describing particular embodiments only and is not intended to be limiting. The terms "comprising", "having" and "including" are to be construed as open-ended terms unless otherwise noted.

[0032] The words / phrases "exemplary", "example", "illustration", "in an instance", "and the like", "and so on", "etc.", "etcetera", "e.g.," , "i.e.," are merely used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein using the words / phrases "exemplary", "example", "illustration", "in an instance", "and the like", "and so on", "etc.", "etcetera", "e.g.," , "i.e.," is not necessarily to be construed as preferred or advantageous over other embodiments.

[0033] Embodiments herein may be described and illustrated in terms of blocks which carry out a described function or functions.　These blocks, which may be referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by a firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.　The circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block.　Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure.　Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.

[0034] It should be noted that elements in the drawings are illustrated for the purposes of this description and ease of understanding and may not have necessarily been drawn to scale. For example, the flowcharts / sequence diagrams illustrate the method in terms of the steps required for understanding of aspects of the embodiments as disclosed herein. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Furthermore, in terms of the system, one or more components / modules which comprise the system may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0035] The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any modifications, equivalents, and substitutes in addition to those which are particularly set out in the accompanying drawings and the corresponding description. Usage of words such as first, second, third etc., to describe components / elements / steps is for the purposes of this description and should not be construed as sequential ordering / placement / occurrence unless specified otherwise.

[0036] The embodiments herein achieve a method for managing an active notification channel in a SEAL notification management service in a wireless network. The method includes detecting, by a notification management client, an expiry timer of the active notification channel being approached and a need for updating a new expiry time associated with the active notification channel with a notification management server. The new expiry time indicates a proposed validity duration for the active notification channel. Further, the method includes sending, by the notification management client, an update notification channel request to the notification management server based on the detection. Further, the method includes receiving, by the notification management client, an update notification channel response including the expiry time for the active notification channel upon validating the valid duration for the active notification channel at the notification management server. Further, the method includes storing, by the notification management client, the new expiry time of the notification management channel at the notification management client.

[0037] The invention proposes new procedure to enable the SNM-C to request UPDATE of the active notification channel with the SNM-S. Further the invention also proposes new message formats that carries the "validity duration" shared by the SNM-C followed by encoding and decoding of these message in the SEAL notification management service.

[0038] This is the first time 3GPP standards has defined notification management service, which shall be reused by services on devices (e.g., UE, or the like) rather than defining their own mechanism to receive notification from a server (or the network). The current invention defines new update procedures to enable the SNM-C to request the UPDATE of the active notification channel "validity duration" with the SNM-S.

[0039] The proposed update notification channel procedures can be used to update the "expiry time" of the active notification channel. But this procedure can be re-used in future for updating other properties of the active notification channel. Like other "user identities", "services or service identities" that wants to re-use the same notification channel. In other word, the current active notification channel procedure shall be re-used to update other properties of the active notification channel with minor enhancements.

[0040] Using same active notification　channel by multiple application services with same user id.　Consider single sign on concept, suppose the user is given a corporate e-mail id to access his mails and is receiving notifications of new mails via the current active notification channel, where the notification channel is associated with the same corporate e-mail id. Further the user can download other applications from his / her Organizations App store and after installation the user opens the newly installed application that prompts to create new user account or re-use corporate e-mail id credential. In later case the SNM-C in the user device shall trigger "Updated active notification channel procedure" towards SNM-S requesting　to associate the new application and its service with existing corporate e-mail id of user, so has to receive notification from new application server associated with newly installed application via the existing active notification channel.

[0041] Embodiments herein disclose an update active notification channel procedure (method) and more specifically to share the expiry timer to update the validity duration of the notification channel. Embodiments herein disclose an "extensible" information element to represent the updated notification channel message, currently representing the expiry timer. In an embodiment herein, the proposed update procedure to notification management services can be extended to support updating of other properties of active notification channel. Embodiments herein disclose a method for the NM-C to encode the expiry timer in an Update Channel request sent towards the NM-S. Embodiments herein disclose a method for the NM-S to decode the expiry timer in the Update Channel request received from the NM-C.

[0042] Referring now to the drawings, and more particularly to FIG. 1 to FIG. 5, where similar reference characters denote corresponding features consistently throughout the figures, there are shown at least one embodiment.

[0043] FIG. 1 illustrates the proposed UPDATE procedure for updating active notification channel initiated by a notification management client (200) towards a notification management server (300) in a wireless network (1000). The wireless network (1000) includes a VAL client (100), the notification management client (200), the notification management server (300) and a VAL server (400). The VAL client (100), the notification management client (200), the notification management server (300) and the VAL server (400) are communicated with each other. Consider that the notification management client (200) has an active notification channel with the notification management server (300).

[0044] In step 1, the notification management client (200) may detect an expiry timer of the active notification channel being approached and a need for updating the new expiry time on notification management server (300). To update the notification channel, in step 2, the notification management client (200) may send an update notification channel request to the notification management server (300) with the proposed new validity duration for the active channel. In step 3, the notification management server (300) may authenticate the notification management client (200) and authorizes its request. In step 4, the notification management server (300) may validate the new proposed expiry timer and sends the notification management client (200) the Update notification channel response with the valid duration for this active notification channel. In step 5, the notification management client (200) shall store the new valid duration of the notification management channel.

[0045] In an embodiment, the proposed update procedure is not restricted for the expiry timer attribute only, it shall also be used to update other properties of the notification channel with suitable modifications.

[0046] Table　1 describes the information flow update notification channel request from the notification management client (200) to the notification management server (300).

[0047] Information elementStatusDescriptionRequestor identityM (Mandatory)Identity of the requesting notification management clientChannel IDMIdentifies the notification channel to be updatedValidity DurationMHow long the notification channel will last (i.e., channel lifetime) as requested by the notification management client.

[0048] Note that the update notification channel request information element can be extended to represent other properties of active notification channel in future, thus enabling a method to update same from the notification management client (200) to the notification management server (300).

[0049] Table　2 describes the information flow update notification channel response from the notification management server (300) to the notification management client (200).

[0050] Information elementStatusDescriptionValidity durationO (Optional)How long the notification channel will last (i.e. channel lifetime) as granted by the notification management server.ResultMIndicates if updating of the channel is success or failure

[0051] FIG. 2 illustrates various hardware components of the notification management client (200), according to the embodiments as disclosed herein. In an embodiment, the notification management client (200) includes a processor (210), a communicator (220), a memory (230) and a SEAL notification management service controller (240). The processor (210) is coupled with the communicator (220), the memory (230) and the SEAL notification management service controller (240).

[0052] The SEAL notification management service controller (240)maydetect the expiry timer of the active notification channel being approached and the need for updating the new expiry time associated with the active notification channel with the notification management server (300). The new expiry time may indicate the proposed validity duration for the active notification channel. Based on the detection, the SEAL notification management service controller (240) may send the update notification channel request to the notification management server (300). Further, the SEAL notification management service controller (240) may receive the update notification channel response including the expiry time for the active notification channel upon validating the valid duration for the active notification channel at the notification management server (300). Further, the SEAL notification management service controller (240) may store the expiry time of the notification management channel at the notification management client (200).

[0053] The SEAL notification management service controller (240) is implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by firmware.

[0054] The processor (210) may include one or a plurality of processors. The one or the plurality of processors may be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an AI-dedicated processor such as a neural processing unit (NPU). The processor (210) may include multiple cores and is configured to execute the instructions stored in the memory (230).

[0055] Further, the processor (210) is configured to execute instructions stored in the memory (230) and to perform various processes. The communicator(220) is configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory (230) also stores instructions to be executed by the processor (210). The memory (230) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory (230) may, in some examples, be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted that the memory (230) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0056] Although the FIG. 2 illustrates various hardware components of the notification management client (200) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the notification management client (200) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purpose and does not limit the scope of the invention. One or more components can be combined together to perform same or substantially similar function in the notification management client (200).

[0057] FIG. 3 illustrates various hardware components of the notification management server (300), according to the embodiments as disclosed herein. In an embodiment, the notification management server (300) includes a processor (310), a communicator (320), a memory (330) and a SEAL notification management service controller (340). The processor (310) is coupled with the communicator (320), the memory (330) and the SEAL notification management service controller (340).

[0058] The SEAL notification management service controller (340) may receive the update notification channel request from the notification management client (200), when the notification management client (200) may detect the expiry timer of the active notification channel being approached and the need for updating the new expiry time associated with the active notification channel with the notification management server (300). The new expiry time may indicate the proposed validity duration for the active notification channel. Further, the SEAL notification management service controller (340) may authenticate the notification management client (200). Further, the SEAL notification management service controller (340) may authorize the update notification channel request. Further, the SEAL notification management service controller (340) may send the update notification channel response including the valid duration with the expiry time value as shared by notification management client (200) or the newly proposed expiry time from notification management server (300) based on a local policy for the active notification channel to the notification management client (200) in reply to the update notification channel request.

[0059] The SEAL notification management service controller (240) may be implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by firmware.

[0060] The processor (310) may include one or a plurality of processors. The one or the plurality of processors may be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an AI-dedicated processor such as a neural processing unit (NPU). The processor (310) may include multiple cores and is configured to execute the instructions stored in the memory (330).

[0061] Further, the processor (310) may be configured to execute instructions stored in the memory (330) and to perform various processes. The communicator(320) may be configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory (330) also stores instructions to be executed by the processor (310). The memory (330) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory (330) may, in some examples, be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted that the memory (330) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0062] Although the FIG. 3 illustrates various hardware components of the notification management server (300) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the notification management server (300) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purpose and does not limit the scope of the invention. One or more components can be combined together to perform same or substantially similar function in the notification management server (300).

[0063] FIG. 4 illustrates a flow chart (S400) illustrating a method, implemented by the notification management client (200), for managing the active notification channel in the SEAL notification management service in the wireless network (1000), according to the embodiments as disclosed herein. The operations (S402-S408) may be handled by the SEAL notification management service controller (240).

[0064] At S402, the method includes detecting the expiry timer of the active notification channel being approached and the need for updating the new expiry time associated with the active notification channel with the notification management server (300). The new expiry time may indicate the proposed validity duration for the active notification channel. At S404, the method includes sending the update notification channel request to the notification management server (300) based on the detection. At S406, the method includes receiving the update notification channel response including the expiry time for the active notification channel upon validating the valid duration for the active notification channel at the notification management server (300). At S408, the method includes storing the new expiry time of the notification management channel at the notification management client (200).

[0065] FIG. 5 illustrates a flow chart (S500) illustrating a method, implemented by the notification management server (300), for managing the active notification channel in the SEAL notification management service in the wireless network (1000), according to the embodiments as disclosed herein. The operations (S502-S508) may be handled by the SEAL notification management service controller (340).

[0066] At S502, the method includes receiving the update notification channel request from the notification management client (200), when the notification management client (200) may detect the expiry timer of the active notification channel being approached and the need for updating the new expiry time associated with the active notification channel with the notification management server (300). The new expiry time may indicate the proposed validity duration for the active notification channel. At S504, the method includes authenticating the notification management client (200). At S506, the method includes authorizing the update notification channel request. At S508, the method includes sending the update notification channel response including the expiry time for the active notification channel to the notification management client (200) based on the update notification channel request.

[0067] The various actions, acts, blocks, steps, or the like in the flow charts (S400 and S500) may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the invention.

[0068] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the elements. The elements can be at least one of a hardware device, or a combination of hardware device and software module.

[0069] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and / or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of at least one embodiment, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.

Claims

1.A method performed by a notification management client for managing an active notification channel in a service enabler architecture layer (SEAL) notification management service in a wireless network, the method comprising:detecting an expiry timer of the active notification channel being approached and a need for updating a new expiry time on a notification management server;transmitting an update notification channel request with a proposed new validity duration for the active notification channel to the notification management server based on the detection;receiving an update notification channel response with a valid duration for the active notification channel based on the update notification channel request, from the notification management server; andstoring the valid duration.2.The method of claim 1, wherein the update notification channel request includes at least one of a requestor identity, a channel identifier (ID) or a validity duration,wherein the requestor identity is identity of the notification management client,wherein the channel ID identifies the notification channel to be updated, andwherein the validity duration indicates a time duration for the notification channel will last as requested by the notification management client.3.The method of claim 1, wherein the update notification channel response includes a result indicating if updating of the active notification channel is success or failure.4.A method performed by a notification management server for managing an active notification channel in a service enabler architecture layer (SEAL) notification management service in a wireless network, the method comprising:receiving an update notification channel request with a proposed new validity duration for the active notification channel from a notification management client, in case that an expiry timer of the active notification channel being approached and a need for updating a new expiry time on the notification management server;authenticating the notification management client;authorizing the update notification channel request; andtransmitting an update notification channel response with a valid duration for the active notification channel, to the notification management client.5.The method of claim 4, further comprising:checking whether a new proposed expiry timer associated with the proposed new validity duration is valid or not.6.The method of claim 4, wherein the update notification channel request includes at least one of a requestor identity, a channel identifier (ID) or a validity duration,wherein the requestor identity is identity of the notification management client,wherein the channel ID identifies the notification channel to be updated, andwherein the validity duration indicates a time duration for the notification channel will last as requested by the notification management client.7.The method of claim 4, wherein the update notification channel response includes a result indicating if updating of the active notification channel is success or failure.8.A notification management client for managing an active notification channel in a service enabler architecture layer (SEAL) notification management service in a wireless network, the notification management client comprising:a transceiver; andat least one processor configured to:detect an expiry timer of the active notification channel being approached and a need for updating a new expiry time on a notification management server,transmit, via the transceiver, an update notification channel request with a proposed new validity duration for the active notification channel to the notification management server based on the detection,receive an update notification channel response with a valid duration for the active notification channel based on the update notification channel request, from the notification management server, andstore the valid duration.9.The notification management client of claim 8, wherein the update notification channel request includes at least one of a requestor identity, a channel identifier (ID) or a validity duration.10.The notification management client of claim 8, wherein the requestor identity is identity of the notification management client,wherein the channel ID identifies the notification channel to be updated, andwherein the validity duration indicates a time duration for the notification channel will last as requested by the notification management client.11.The notification management client of claim 8, wherein the update notification channel response includes a result indicating if updating of the active notification channel is success or failure.12.A notification management server for managing an active notification channel in a service enabler architecture layer (SEAL) notification management service in a wireless network, the notification management server comprising:a transceiver; andat least one processor configured to:receive, via the transceiver, an update notification channel request with a proposed new validity duration for the active notification channel from a notification management client, in case that an expiry timer of the active notification channel being approached and a need for updating a new expiry time on the notification management server,authenticate the notification management client,authorize the update notification channel request, andtransmit an update notification channel response with a valid duration for the active notification channel, to the notification management client.13.The notification management server of claim 12, wherein the at least one processor is further configured to:check whether a new proposed expiry timer associated with the proposed new validity duration is valid or not.14.The notification management server of claim 12, wherein the update notification channel request includes at least one of a requestor identity, a channel identifier (ID) or a validity duration,wherein the requestor identity is identity of the notification management client,wherein the channel ID identifies the notification channel to be updated, andwherein the validity duration indicates a time duration for the notification channel will last as requested by the notification management client.15.The notification management server of claim 12, wherein the update notification channel response includes a result indicating if updating of the active notification channel is success or failure.

Images