Search

EP-4470194-B1 - SYSTEM AND METHOD FOR ENABLING NOTIFICATION MANAGEMENT IN AS SEAL SERVICE IN A WIRELESS COMMUNICATION SYSTEM

EP4470194B1EP 4470194 B1EP4470194 B1EP 4470194B1EP-4470194-B1

Inventors

  • RAMAMOORTHY, ARUNPRASATH
  • PATTAN, BASAVARAJ JAYAWANT
  • SHAH, Sapan Pramodkumar

Dates

Publication Date
20260506
Application Date
20230322

Claims (15)

  1. A method performed by a notification management client in a wireless communication system, the method comprising: receiving, from a vertical application layer, VAL, client, a notification management request message to receive a notification from a VAL server (402); transmitting, to a notification management server, a create notification channel request message for a notification channe (404); receiving, from the notification management server, a create notification channel response message (404) including a callback uniform resource locator, URL; transmitting, to the notification management server, an open notification channel message (408) to start receiving a notification message based on the create notification channel response message; transmitting, to the VAL client, a notification management response message including an indication of status of success or failure to start receiving the notification and the callback URL (410); receiving, from the notification management server, a notification message (420) including a VAL client ID and a VAL service ID; and transmitting, to the VAL client, the notification message (422), wherein the callback URL is associated with an endpoint for receiving the notification message from the VAL server.
  2. The method of claim 1, wherein the create notification channel request message includes a desired validity duration of the notification channel and a notification channel type, and wherein a type of notification channel is one of PUSH or PULL.
  3. The method of claim 1, further comprising: transmitting, to the notification management server, request to start a PUSH notification service in case that a notification type is a PUSH method.
  4. The method of claim 1, further comprising: receiving, from the VAL client, stop receiving notification management request message to stop receiving notification from the VAL server; transmitting, to the notification management server, delete notification channel request message for deleting the notification channel; receiving, from the notification management server, delete notification channel response message; and transmitting, to the VAL client, an indication of status of the stop receiving notification management request, wherein the indication of status of the stop receiving notification management request indicates success or failure of deletion of the at least one notification channel.
  5. A method performed by a notification management server in a wireless communication system, the method comprising: receiving, from a notification management client, a create notification channel request message (404) for a notification channel based on a notification management request message; transmitting, to the notification management client, a create notification channel response message (406) including a callback uniform resource locator, URL; receiving, from the notification management client, an open notification channel message (408) to start receiving a notification message based on the create notification channel response message; receiving, from the VAL server, a notification message (420) including a VAL client ID and VAL service ID, generated from the VAL server; and transmitting, to the notification management client, the notification message (422) wherein the callback URL is associated with an endpoint for receiving the notification message from the VAL server.
  6. The method of claim 5, wherein the create notification channel request message includes a desired validity duration of the notification channel and a notification channel type, wherein a type of notification channel is one of PUSH or PULL.
  7. The method of claim 5, further comprising: receiving, from the notification management client, request to start a PUSH notification service in case that a notification type is a PUSH method.
  8. The method of claim 5, further comprising: receiving, from the notification management client, delete notification channel request message for deleting the notification channel based on stop receiving notification management request message; and transmitting, to the notification management client, delete notification channel response message.
  9. A notification management client in a wireless communication system, the notification management client of the notification management client comprising: a transceiver, and a controller coupled with the transceiver and configured to: receive, by a notification management client from a vertical application layer, VAL, client, a notification management request message to receive a notification from a VAL server, transmit, to a notification management server, a create notification channel request message for a notification channel, receive, from the notification management server, a create notification channel response message including a callback uniform resource locator, URL, transmit, to the notification management server, an open notification channel message to start receiving a notification message based on the create notification channel response message, transmit, to the VAL client, a notification management response message including an indication of status of success or failure to start receiving the notification and the callback URL, receive, from the notification management server, a notification message including a VAL client ID and a VAL service ID, and transmit, to the VAL client, the notification message, wherein the callback URL is associated with an endpoint for receiving the notification message from the VAL server.
  10. The notification management client of claim 9, wherein the controller is further configured to: wherein the create notification channel request message includes a desired validity duration of the notification channel and a notification channel type, and wherein a type of notification channel is one of PUSH or PULL.
  11. The notification management client of claim 9, wherein the controller is further configured to: transmit, to the notification management server, request to start a PUSH notification service in case that a notification type is a PUSH method.
  12. The notification management client of claim 9, wherein the controller is further configured to: receive, from the VAL client, stop receiving notification management request message to stop receiving notification from the VAL server, transmit, to the notification management server, delete notification channel request message for deleting the notification channel, receive, from the notification management server, delete notification channel response message, and transmit, to the VAL client, an indication of status of the stop receiving notification management request, wherein the indication of status of the stop receiving notification management request indicates success or failure of deletion of the at least one notification channel.
  13. A notification management server in a wireless communication system, the server comprising: a transceiver, and a controller coupled with the transceiver and configured to: receive, from a notification management client, a create notification channel request message for a notification channel based on a notification management request message, transmit, to the notification management client, a create notification channel response message including a callback uniform resource locator, URL, receive, from the notification management client, an open notification channel message to start receiving a notification message based on the create notification channel response message, receive, from the VAL server, a notification message including a VAL client ID and VAL service ID, generated from the VAL server, and transmit, to the notification management client, the notification message, wherein the callback URL is associated with an endpoint for receiving the notification message from the VAL server.
  14. The server of claim 13, wherein the create notification channel request message includes a desired validity duration of the notification channel and a notification channel type, wherein a type of notification channel is one of PUSH or PULL.
  15. The server of claim 13, wherein the controller is further configured to: receive, from the notification management client, request to start a PUSH notification service in case that a notification type is a PUSH method.

Description

[Technical Field] Embodiments disclosed herein relate to wireless communication system, and more specifically, the present disclosure relates to systems and methods for enabling subscription and notification mechanism in a Service Enabler Architecture Layer (SEAL) service which can be leveraged by vertical applications. [Background Art] 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 (THz) 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. 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 transmi ssion 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. 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. 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. 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. 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-dimensi