Methods and systems for deleting the active notification channel in service enabler architecture layer (SEAL) notification management service
The implementation of HTTP protocol-based methods for deleting active notification channels in the SEAL Notification Management service addresses the lack of deletion procedures in 5G systems, optimizing resource usage and network performance by ensuring complete channel deletion and preventing future message pushing.
Patent Information
- Application Number
- PCT/KR2024/006453
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-12
- Filing Date
- 2024-05-13
- Publication Date
- 2024-11-21
AI Technical Summary
Current 5G mobile communication systems lack procedures for deleting active notification channels in the Service Enabler Architecture Layer (SEAL) Notification Management service, leading to maintenance overhead and resource consumption on both the client and server sides due to unused notification channels.
Implementing HTTP protocol-based methods for the SEAL Notification Management Client (SNM-C) to request the deletion of active notification channels with the SEAL Notification Management Server (SNM-S), including specific message formats and encoding schemes to ensure complete deletion of notification channels and prevent future message pushing.
This solution effectively deletes active notification channels, conserving resources such as memory, processor usage, and power by eliminating unused channels, thereby reducing maintenance overhead and optimizing network performance.
Smart Images

Figure KR2024006453_21112024_PF_FP_ABST
Abstract
Description
METHODS AND SYSTEMS FOR DELETING THE ACTIVE NOTIFICATION CHANNEL IN SERVICE ENABLER ARCHITECTURE LAYER (SEAL) NOTIFICATION MANAGEMENT SERVICE
[0001] Embodiments disclosed herein relate to a communication network, and more particularly to delete or deregister an active notification channel in a Service Enabler Architecture Layer (SEAL) Notification Management service.
[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 application (e.g., chat application, social networking application or the like) running on a user Equipment (UE) (e.g. smart phone, 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, since each VAL server is deployed in different regions running on internet protocol (IP) address and ports which are obvious to be different. Due to continuous listening from the UE for notification also leads in consuming more computing resources, and power on the UE.
[0009] In a 3rdGeneration Partnership Project (3GPP) technical specification (TS) 24.542, SEAL Notification Management service defines a notification mechanism to be consumed by the application mentioned in background 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 a callback associated with the SNM-S.
[0010] Currently the specification defines procedures to provide the notification channel with callback associated with the SNM-S when the SNM-C creates a notification channel with the SNM-S. The applications running on the UE can use the notification channel by sharing callback associated with the SNM-S to their VAL servers for pushing future notification messages through the SNM-S. Thus, the SEAL notification Management offloads the responsibility of notification management performed by each application on the UE and realizes the same with simplified approach with just few (or one) notification channel between the SNM-C and the SNM-S.
[0011] But the 3GPP TS 24.542 for the notification management has not defined any procedures to DELETE the active notification channel between the SNM-C and the SNM-S. Hence, the SNM-C on the UE still maintains the active notification channel with the SNM-S, though the application requests the SNM-C to stop receiving notification messages through the notification channel. This results in maintaining unused notification channel leading to a maintenance overhead on both SNM-S and SNM-C that requires resources like power, processor usage and memory.
[0012] 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.
[0013] The principal object of the embodiments herein is to disclose methods and systems for deleting an active notification channel in a SEAL Notification Management service, wherein embodiments herein propose high-level procedures using a HTTP protocol to enable a SEAL Notification Management Client (SNM-C) to request DELETE (or partial de-register) of the active notification channel with the SNM-S.
[0014] Another object of the embodiments herein is to disclose methods and systems for deleting the active notification channel in the SEAL notification management service, wherein in case of DELETE, the notification channel is completely deleted and there will be no future notification messages pushed by the SEAL Notification Management Server (SNM-S).
[0015] Another object of the embodiments herein is to disclose message formats to convey deletion or de-register of notification channel followed by encoding and decoding of these message formats in the SEAL notification management service.
[0016] 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 scope thereof, and the embodiments herein include all such modifications.
[0017] Accordingly, the embodiments herein provide methods for deleting or de-register an active notification channel in a SEAL notification management service. The method includes sending, by a SNM-C, a Hypertext Transfer Protocol (HTTP) DELETE request to a SNM-S upon receiving a request from a Vertical Application Layer (VAL) service to stop receiving a notification via a notification channel. Further, the method includes receiving, by the SNM-C, an HTTP 200 OK response from the SNM-S for the HTTP DELETE request upon deleting the active notification channel at the SNM-S based on the HTTP DELETE request.
[0018] In an embodiment, the SNM-C sets a request- Uniform Resource Identifier (URI) to a URI of the SNM-S in the HTTP DELETE request.
[0019] In an embodiment, the SNM-C includes a content-type header field set to "application / vnd.3gpp.seal-delete-notification-channel-request" in the HTTP DELETE request. The SNM-C generate a delete notification channel request message.
[0020] In an embodiment, the SNM-C shall set the delete notification channel request message with the requestor identity to a notification management client identity. The delete notification channel request message sets a channel identifier to an identity of the corresponding notification channel with the SNM-S to be deleted.
[0021] In an embodiment, the SNM-C sets a VAL identity cluster information parameter with VAL identities in the delete notification channel request message corresponding to the VAL service requesting to stop receiving notifications, which indicates SNM-C prefers to deregister a notification channel for these identities represented in the VAL identity cluster information parameter instead of deleting the notification channel, when other VAL services use the same notification channel in a User Equipment (UE).
[0022] In an embodiment, the SNM-C does not set VAL identity cluster information parameter with VAL identities in the delete notification channel request message corresponding to the VAL service requesting to stop receiving notifications, which indicates SNM-C prefers to delete the notification channel based on the channel identifier, when there are no other VAL services using the same notification channel in a UE.
[0023] Accordingly, the embodiments herein provide methods for deleting an active notification channel in a SEAL notification management service. The method includes receiving, by a SNM-S, a HTTP DELETE request from a SNM-C in which a request Uniform Resource Identifier (URI) of the HTTP DELETE request includes a URI of the SNM-S. Further, the method includes sending, by the SNM-S, an HTTP 200 OK response to the SNM-C for the HTTP DELETE request.
[0024] In an embodiment, the SNM-S responds with an HTTP error response to the HTTP DELETE request, when an identity of a sender of the received HTTP DELETE request is not an authorized user.
[0025] In an embodiment, the SNM-S is configured to determine whether a notification channel corresponding to a channel identifier exists or not. Further, the SNM-S is configured to respond with an HTTP error response to the HTTP DELETE request if the notification channel does not exist.
[0026] In an embodiment, when the SNM-S fails to process the HTTP DELETE request received from the SNM-C, the SNM-S shall HTTP response with an appropriate HTTP Error code that conveys the reason for failure.
[0027] In an embodiment, the SNM-S is configured to delete the notification channel if the VAL identity cluster information parameter is not provided in the delete notification channel request message.
[0028] Accordingly, the embodiments herein provide a SNM-C including an active notification channel deleting controller coupled with a processor and a memory. The active notification channel deleting controller is configured to send a HTTP DELETE request to a SNM-S upon receiving a request from a VAL service to stop receiving a notification via a notification channel. Further, the active notification channel deleting controller is configured to receive an HTTP 200 OK response from the SNM-S for the HTTP DELETE request upon deleting the active notification channel at the SNM-S based on the HTTP DELETE request.
[0029] Accordingly, the embodiments herein provide a SNM-S including an active notification channel deleting controller coupled with a processor and a memory. The active notification channel deleting controller is configured to receive a HTTP DELETE request from a SNM-C in which a request URI of the HTTP DELETE request includes a URI of the SNM-S. Further, the active notification channel deleting controller is configured to send an HTTP 200 OK response to the SNM-C for the HTTP DELETE request.
[0030] According to an embodiment of present disclosure, methods and systems for deleting an active notification channel in a SEAL Notification Management service are provided.
[0031] The embodiments of the disclosure itself, as well as a preferred mode of use, further objectives and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings. One or more embodiments are now described, by way of example only, with reference to the accompanying drawings in which:
[0032] FIG. 1 illustrates a sequence diagram illustrating a system for deleting an active notification channel in a SEAL notification management service, according to the embodiments as disclosed herein.
[0033] FIG. 2 illustrates various hardware components of a SNM-C, according to the embodiments as disclosed herein.
[0034] FIG. 3 illustrates various hardware components of a SNM-S, according to the embodiments as disclosed herein.
[0035] FIG. 4 illustrates a flow chart illustrating a method, implemented by the SNM-C, for deleting the active notification channel in the SEAL notification management service, according to the embodiments as disclosed herein.
[0036] FIG. 5 illustrates a flow chart illustrating a method, implemented by the SNM-S, for deleting the active notification channel in the SEAL notification management service, according to the embodiments as disclosed herein.
[0037] 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.
[0038] In the present document, the word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.
[0039] While the disclosure is susceptible to various modifications and alternative forms, specific embodiment thereof has been shown by way of example in the drawings and will be described in detail below. It should be understood, however that it is not intended to limit the disclosure to the particular forms disclosed, but on the contrary, the disclosure is to cover all modifications, equivalents, and alternative falling within the scope of the disclosure.
[0040] The terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, device or method that comprises a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or device or method. In other words, one or more elements in a device or system or apparatus proceeded by "comprises... a" does not, without more constraints, preclude the existence of other elements or additional elements in the device or system or apparatus.
[0041] In the following detailed description of the embodiments of the disclosure, reference is made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration specific embodiments in which the disclosure may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, and it is to be understood that other embodiments may be utilized and that changes may be made without departing from the scope of the present disclosure. The following description is, therefore, not to be taken in a limiting sense.
[0042] 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.
[0043] 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.
[0044] 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.
[0045] 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.
[0046] 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.
[0047] Embodiments herein disclose methods and systems for deleting the active notification channel in a SEAL Notification Management service, wherein embodiments herein propose high-level procedures using a HTTP protocol to enable a SNM-C to request DELETE (or partial de-register) of the active notification channel with the SNM-S. In case of DELETE, the notification channel is completely deleted and there will be no future notification messages pushed by the SNM-S.
[0048] Embodiments herein define procedures to enable the SNM-C to request DELETE (or partial de-register) the active notification channel with the SNM-S.
[0049] Embodiments herein define an "extensible" information element, wherein the element can be used to represent the delete notification channel request message.
[0050] Embodiments herein propose a "encoding scheme", that shall be included in the Content-Type header field of HTTP DELETE request as defined below: "application / vnd.3gpp.seal-delete-notification-channel-request".
[0051] Embodiments herein disclose a method for the SNM-C to encode the delete notification channel request information element sent in the HTTP DELETE channel request body sent towards the SNM-S
[0052] Embodiments herein disclose a method for the SNM-S to decode the delete notification channel request information element received in the HTTP DELETE channel request body from the SNM-C.
[0053] The proposed method can be used to delete the active notification channel between SNM-C and SNM-S, so as to preserve resources (e.g., memory, bandwidth or the like) at both SNM-S and SNM-C.
[0054] Referring now to the drawings, and more particularly to FIGS. 1 through 5, where similar reference characters denote corresponding features consistently throughout the figures, there are shown at least one embodiment.
[0055] FIG. 1 illustrates a sequence diagram illustrating a system (130) for deleting an active notification channel in a SEAL notification management service, according to the embodiments as disclosed herein.
[0056] At step 1, the SNM-C (130) may send a HTTP DELETE with delete notification channel information to the SNM-S (140). At step 2, the SNM-S (140) may process the delete notification channel information received from the SNM-C (130). At step 3, the SNM-S (140) may determine whether the notification channel exists or not. Further, the SNM-S (140) may delete the notification channel if the VAL identity cluster information parameter is not provided. Else, the SNM-S (140) may proceed to only deregister the notification channel for those identities shared in VAL identity cluster info parameter corresponding to the VAL service.
[0057] At step 4, the SNM-S (140) may trigger the response to the SNM-C (130) for delete notification channel. At step 5, the SNM-S (140) may send the response to the HTTP POST request for delete notification channel to the SNM-C (130). At step 6, the SNM-C (130) may decode the delete notification channel response from the SNM-S (140). At step 7, the SNM-C (130) may share the delete notification channel response to the VAL client (120). At step 8, the VAL client (120) may remove the SNM-S (140) callback URI from a VAL server (150), that was shared previously.
[0058] Notification channel deletion procedures:
[0059] SNM client procedures: Upon receiving a request from the VAL service to stop receiving notifications via the notification channel, the SNM-C (130) shall delete the notification channel by sending an HTTP DELETE request to the SNM-S (140). In the HTTP DELETE request, the SNM-C (130):
[0060] a) shall set the Request-URI to the URI of the SNM-S (140);
[0061] b) shall include a Host header with public user identity of the SNM-S (140);
[0062] c) shall include an Authorization header field with the "Bearer" authentication scheme set to an access token of the "bearer" token type as specified in Internet Engineering Task Force (IETF) Request for Comments (RFC) 6750;
[0063] d) shall include a Content-Type header field set to "application / vnd.3gpp.seal-delete-notification-channel-request";
[0064] e) shall generate the delete notification channel request message as specified in Table 2:
[0065] 1) shall set the requestor identity to the notification management client identity;
[0066] 2) shall set the channel identifier to the identity of the corresponding notification channel with the SNM-S (140) to be deleted. If other VAL services use the same channel in the UE (110), then SNM-C (130):
[0067] i) may set the VAL identity cluster info parameter with VAL identities corresponding to the VAL service requesting to stop receiving notifications specified in Table 2, which indicates SNM-C (130) prefers to deregister the notification channel for these identities rather than deletion of the notification channel; and
[0068] f) include the parameters specified in Table 1 serialized into a JavaScript Object Notation (JSON) structure as specified in IETF RFC 7159.
[0069] SNM server procedures: Upon reception of the HTTP DELETE request from the SNM-C (130) where the Request-URI of the HTTP DELETE request contains the URI of the SNM-S (140), the SNM-S (140):
[0070] a) shall determine the requestor identity of the received HTTP DELETE request as specified in clause 6.2.1.1, and:
[0071] 1) if the identity of the sender of the received HTTP DELETE request is not authorized user, shall respond with an HTTP 403 (Forbidden) response to the HTTP DELETE request and skip rest of the steps;
[0072] b) shall determine whether notification channel corresponding to the channel identifier exists or not; and:
[0073] 1) if notification channel does not exist, shall respond with an HTTP 406 (Not Acceptable) response to the HTTP DELETE request and skip rest of the steps;
[0074] c) shall delete the notification channel if the VAL identity cluster info parameter is not provided else proceed to only deregister the notification channel for these identities shared in VAL identity cluster info parameter corresponding to VAL service; and
[0075] c) shall send an HTTP 200 (OK) response to the SNM-C (130).
[0076] Delete notification channel:
[0077] General:
[0078] Embodiments herein provide a normative description of the parameters, which will be sent by the SNM-C (130) to the SNM-S (140) as part of delete notification channel request over notification channel.
[0079] Client-side parameters: The SNM-C (130) shall convey the following parameters while sending request for delete notification channel request.
[0080] Table 1 depicts client side parameters for delete notification channel request.
[0081] ParameterDescriptionRequestor identityREQUIRED. Represents the identity of the notification management clientChannel IdentifierREQUIRED. Represents the identifier of the notification channel corresponding to the SNM-C to be deletedVAL Identity Cluster InfoOPTIONAL. Represents the VAL identities to be deregistered from the notification channel encoded as specified in Table 2.
[0082] Table 2 depicts the VAL Identity Cluster Information.
[0083] ParameterDescriptionVAL User IdentityREQUIRED. Represents the identity of VAL user within the VAL service.VAL Service IDREQUIRED. Represents the Identify of the VAL service.VAL Application IDREQUIRED. Represents the Identity of the VAL application residing in the VAL UE.
[0084] FIG. 2 illustrates various hardware components of the SNM-C (130), according to the embodiments as disclosed herein. In an embodiment, the SNM-C (130) includes a processor (210), a communicator (220), a memory (230) and an active notification channel deleting controller (240). The processor (210) is coupled with the communicator (220), the memory (230) and the active notification channel deleting controller (240).
[0085] The active notification channel deleting controller (240) may send the HTTP DELETE request to the SNM-S (140) upon receiving the request from the VAL service to stop receiving the notification via the notification channel. Further, the active notification channel deleting controller (240) may receive the HTTP 200 OK response from the SNM-S (140) for the HTTP DELETE request upon deleting the active notification channel at the SNM-S (140) based on the HTTP DELETE request.
[0086] In an embodiment, the active notification channel deleting controller (240) may set the request- URI to the URI of the SNM-S (140) in the HTTP DELETE request.
[0087] In an embodiment, the SNM-C (130) may include the content-type header field set to "application / vnd.3gpp.seal-delete-notification-channel-request" in the HTTP DELETE request. The active notification channel deleting controller (240) may generate the delete notification channel request message. In an embodiment, the delete notification channel request message may set the requestor identity to the notification management client identity. The delete notification channel request message may set the channel identifier to the identity of the corresponding notification channel with the SNM-S (140) to be deleted.
[0088] In an embodiment, the active notification channel deleting controller (240) may set the VAL identity cluster information parameter with the VAL identities in the delete notification channel request message corresponding to the VAL service requesting to stop receiving notifications, which indicates SNM-C (130) prefers to deregister a notification channel for these identities represented in the VAL identity cluster information parameter instead of deleting the notification channel, when other VAL services use the same notification channel in a User Equipment (UE).
[0089] In an embodiment, the active notification channel deleting controller (240) does not set VAL identity cluster information parameter with VAL identities in the delete notification channel request message corresponding to the VAL service requesting to stop receiving notifications, which indicates SNM-C (130) prefers to delete the notification channel based on the channel identifier, when there is no other VAL services using the same notification channel in a User Equipment (UE).
[0090] The active notification channel deleting 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.
[0091] 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).
[0092] 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).
[0093] Although FIG. 2 illustrates various hardware components of the SNM-C (130) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the SNM-C (130) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purposes and does not limit the scope of the invention. One or more components can be combined together to perform the same or substantially similar function in the SNM-C (130).
[0094] FIG. 3 illustrates various hardware components of the SNM-S (140), according to the embodiments as disclosed herein. In an embodiment, the SNM-S (140) includes a processor (310), a communicator (320), a memory (330) and an active notification channel deleting controller (340). The processor (310) is coupled with the communicator (320), the memory (330) and the active notification channel deleting controller (340).
[0095] The active notification channel deleting controller (340) may receive the HTTP DELETE request from the SNM-C (130) in which the request URI of the HTTP DELETE request includes the URI of the SNM-S (140). Further, the active notification channel deleting controller (340) may send the HTTP 200 OK response to the SNM-C (130) for the HTTP DELETE request.
[0096] In an embodiment, the active notification channel deleting controller (340) may respond with the HTTP error response to the HTTP DELETE request, when the identity of the sender of the received HTTP DELETE request is not the authorized user.
[0097] In an embodiment, the active notification channel deleting controller (340) may be configured to determine whether the notification channel corresponding to the channel identifier exists or not. Further, the active notification channel deleting controller (340) may be configured to respond with the HTTP error response to the HTTP DELETE request if the notification channel does not exist.
[0098] In an embodiment, the active notification channel deleting controller (340) may delete the notification channel if the VAL identity cluster information parameter is not provided in the delete notification channel request message.
[0099] The active notification channel deleting controller (340) 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.
[0100] 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).
[0101] Further, the processor (310) is configured to execute instructions stored in the memory (330) and to perform various processes. The communicator(320) is 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).
[0102] Although FIG. 3 illustates various hardware components of the SNM-S (140) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the SNM-S (140) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purposes and does not limit the scope of the invention. One or more components can be combined together to perform the same or substantially similar function in the SNM-S (140).
[0103] FIG. 4 illustrates a flow chart (S400) illustrating a method, implemented by the SNM-C (130), for deleting the active notification channel in the SEAL notification management service, according to the embodiments as disclosed herein. The operations (S402 and S404) may be handled by the active notification channel deleting controller (240).
[0104] At S402, the method includes sending the HTTP DELETE request to the SNM-S (140) upon receiving the request from the VAL service to stop receiving the notification via the notification channel. At S404, the method includes receiving the HTTP 200 OK response from the SNM-S (140) for the HTTP DELETE request upon deleting the active notification channel at the SNM-S (140) based on the HTTP DELETE request.
[0105] FIG. 5 illustrates a flow chart (S500) illustrating a method, implemented by the SNM-S (140), for deleting the active notification channel in the SEAL notification management service, according to the embodiments as disclosed herein. The operations (S502 and S504) may be handled by the active notification channel deleting controller (340).
[0106] At S502, the method includes receiving the HTTP DELETE request from the SNM-C (130) in which the request URI of the HTTP DELETE request includes the URI of the SNM-S (140). At S504, the method includes sending the HTTP 200 OK response to the SNM-C (130) for the HTTP DELETE request.
[0107] The proposed method can be used to delete the active notification channel between the SNM-C (130) and the SNM-S (140), so as to preserve resources (e.g., memory, bandwidth or the like) at the SNM-C (130) and the SNM-S (140).
[0108] 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.
[0109] 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.
[0110] 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 scope of the embodiments as described herein.
Claims
1.A method performed by a terminal for deleting an active notification channel in a service enabler architecture layer (SEAL) notification management service, the method comprising:receiving, by a SEAL notification management client (SNM-C), a request from a vertical application layer (VAL) service to stop receiving a notification via a notification channel;transmitting, by the SNM-C, a hypertext transfer protocol (HTTP) DELETE request to an SNM-server (SNM-S) based on the request; andreceiving, by the SNM-C (130), an HTTP 200 OK response from the SNM-S for the HTTP DELETE request upon deleting the active notification channel at the SNM-S based on the HTTP DELETE request.2.The method of claim 1, further comprising:setting, by the SNM-C, a request- uniform resource identifier (URI) to a URI of the SNM-S in the HTTP DELETE request.3.The method of claim 1, further comprising:generating, by the SNM-C, a delete notification channel request message,wherein a content-type header field is set to "application / vnd.3gpp.seal-delete-notification-channel-request" in the HTTP DELETE request.4.A method performed by a service enabler architecture layer (SEAL) notification management server (SNM-S), the method comprising:receiving, from a SEAL notification management client (SNM-C), a hypertext transfer protocol (HTTP) DELETE request, wherein a request uniform resource identifier (URI) of the HTTP DELETE request comprises a URI of the SNM-S; andtransmitting, to the SNM-C, an HTTP 200 OK response for the HTTP DELETE request upon deleting the active notification channel at the SNM-S based on the HTTP DELETE request.5.The method of claim 4, further comprising:responding, to the SNM-C, an HTTP error response to the HTTP DELETE request, in case that an identity of a sender of the received HTTP DELETE request is not an authorized user.6.The method of claim 4, further comprising:determining whether a notification channel corresponding to a channel identifier exists or not; andresponding an HTTP error response to the HTTP DELETE request in case that the notification channel does not exist.7.The method of claim 4, wherein the SNM-S (140) is configured to delete the notification channel in case that the VAL identity cluster information parameter is not provided in the delete notification channel request message.8.A service enabler architecture layer (SEAL) notification management client (SNM-C), comprising:a processor;a memory; andat least one processor coupled with the processor and the memory, configured to:receive a request from a vertical application layer (VAL) service to stop receiving a notification via a notification channel;transmit a hypertext transfer protocol (HTTP) DELETE request to an SNM-Server (SNM-S) based on the request ; andreceive an HTTP 200 OK response from the SNM-S for the HTTP DELETE request upon deleting the active notification channel at the SNM-S based on the HTTP DELETE request.9.The SNM-C of claim 8, wherein the at least one processor is further configured to:set a request- uniform resource identifier (URI) to a URI of the SNM-S in the HTTP DELETE request.10.The SNM-C of claim 8, wherein the at least one processor is further configured to:generate a delete notification channel request message,wherein a content-type header field is set to "application / vnd.3gpp.seal-delete-notification-channel-request" in the HTTP DELETE request.11.A service enabler architecture layer (SEAL) notification management server (SNM-S), comprising:a processor;a memory; andat least one processor coupled with the processor and the memory, configured to:receive, from a SEAL notification management client (SNM-C), a hypertext transfer protocol (HTTP) DELETE request, wherein a request uniform resource identifier (URI) of the HTTP DELETE request comprises a URI of the SNM-S; andtransmit, to the SNM-C, an HTTP 200 OK response for the HTTP DELETE request upon deleting the active notification channel at the SNM-S based on the HTTP DELETE request.12.The SNM-S of claim 11, wherein the at least one processor is further configured to:respond, to the SNM-C, an HTTP error response to the HTTP DELETE request, in case that an identity of a sender of the received HTTP DELETE request is not an authorized user.13.The SNM-S of claim 11, wherein the at least one processor is further configured to:determine whether a notification channel corresponding to a channel identifier exists or not, andrespond an HTTP error response to the HTTP DELETE request in case that the notification channel does not exist.14.The SNM-S of claim 11, wherein the SNM-S (140) is configured to delete the notification channel in case that the VAL identity cluster information parameter is not provided in the delete notification channel request message.
Citation Information
Patent Citations
Method Of Handling Notification Channel Disconnection
US20160150027A1
Filters for bulk subscriptions
US20220272619A1
