Method and system for providing framework by IP multimedia subsystem

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method includes receiving a registration message from a Serving Call Session Control Function (S-CSCF). The method includes determining whether a plurality of conditions meets predefined criteria associated with an IP Multimedia Subsystem Application Server (IMS-AS), and registering an address of the IMS-AS in a Home Subscriber Server (HSS) in response to determining that the plurality of conditions meets predefined criteria associated with the IMS-AS. The method includes receiving a subscription request from HSS for one or more IP multimedia subsystem Data Channel (IMS DC) events associated with the IMS-AS, and detecting that the one or more IMS DC events occur at the IMS-AS. The method includes transmitting the one or more notifications associated with the IMS DC events to at least one of the third party or network function and the HSS.

Description

METHOD AND SYSTEM FOR PROVIDING FRAMEWORK BY IP MULTIMEDIA SUBSYSTEM

[0001] The present invention generally relates to the field of wireless communication systems, and more specifically relates to a method and a system for providing a framework by IP Multimedia Subsystem (IMS).

[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] The information disclosed in this background section is only for the enhancement of understanding of the general background of the disclosure and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.

[0009] The Internet Protocol Multimedia Subsystem (IMS) has been operational for an extended period, with major telecommunications operators establishing networks to deliver a range of services, including Voice over Long-Term Evolution (VoLTE). Currently, the IMS is undergoing evolution to align with the requirements of 5G networks, facilitating the introduction of new services through an IMS Data Channel (IMS DC) in conjunction with voice and video communications. The IMS DC accommodates various applications, such as remote support, remote surgery, remote examinations, Augmented Reality (AR) with control capabilities, machine control, and Virtual Reality (VR) with collaborative features.

[0010] For instance, in a modern hospital, a surgeon in a metropolitan area needs to perform complex surgery on a patient located in a rural clinic. To enhance the surgical procedure, the hospital utilizes the IMS DC to establish a seamless connection between the two locations. The surgeon initiates a remote surgery session using a specialized application that operates over the IMS DC. This application allows the surgeon to access high-definition video feeds from the surgical room in the rural clinic, providing real-time visuals of the patient and the surgical team.

[0011] Further, the 3rdGeneration Partnership Project (3GPP) SA4 Working Group (WG) has conducted investigations into the capabilities of the IMS DC, leading to updates in Technical Specification (TS) 26.114, which delineate the realization of the IMS DC. Additionally, the SA2 WG has provided the architectural framework for the IMS DC. However, several challenges / issues exist within the current IMS framework, which are mentioned herein. In Release 19, 3GPP SA2 is examining two Key Issues (KIs) related to the provision of a mechanism through which third-party entities or network functions can subscribe to and receive event notifications concerning IMS DC for individual subscribers or groups of subscribers.

[0012] According to Technical Report (TR) 23.700-77, the first key issue explores necessary architectural enhancements to the IMS framework to facilitate an extensible mechanism that enables applications to subscribe to and receive notifications regarding IMS events (e.g., surgical procedure) associated with IMS services within the context of DC communication. This encompasses the identification of IMS events available for subscription by Network Functions (NFs) or Application Functions (AFs), which may pertain to specific IMS subscribers or designated lists of subscribers, as well as the development of event subscription mechanisms to ascertain the IMS NFs or nodes serving the particular subscribers for which event notifications have been requested.

[0013] For instance, in the modern hospital, the IMS manages surgical procedures, patient records, and communication among departments. However, the existing IMS framework does not support real-time notifications for critical surgical events, leading to communication delays among surgical teams and support staff. It is essential to identify key surgical events that require immediate notifications, such as when a surgery is scheduled, underway, or completed, or when there are updates regarding a patient's post-operative condition. Additionally, there is a need for an enhanced solution that allows NFs and AFs to subscribe to these notifications based on their specific roles. For example, surgical teams could receive alerts about ongoing and completed surgeries, while nursing staff would benefit from updates on postoperative patients. Moreover, a new notification system is necessary to ensure that these alerts are delivered promptly and reliably to the relevant personnel.

[0014] The second key issue focuses on the implications for an IMS architecture, interfaces, and procedures necessary to support the exposure of IMS capabilities in relation to IMS DC sessions. In other words, there is a need for the IMS architecture, which enhances to support the above-mentioned new features.

[0015] Thus, it is desired to address the above-mentioned disadvantages or other shortcomings or at least provide a useful alternative for the IMS.

[0016] The existing IMS framework does not support real-time notifications. Additionally, there is a need for an enhanced solution that allows NFs and AFs to subscribe to these notifications based on their specific roles

[0017] This summary is provided to introduce a selection of concepts, in a simplified format, that are further described in the detailed description of the invention. This summary is neither intended to identify key or essential inventive concepts of the invention nor is it intended for determining the scope of the invention.

[0018] According to one embodiment of the present disclosure, a method for handling one or more notifications within an IP Multimedia Subsystem (IMS) architecture is disclosed herein. The method includes receiving, by an IMS Application Server (IMS-AS), a registration message from a Serving Call Session Control Function (S-CSCF), wherein the registration message comprises an IP Multimedia Public Identity (IMPU). The method further includes determining, upon receiving the registration message, by the IMS-AS, whether a plurality of conditions meets predefined criteria associated with the IMS-AS. The method further includes registering, by the IMS-AS, an address of the IMS-AS in a Home Subscriber Server (HSS) in response to determining that the plurality of conditions meets predefined criteria associated with the IMS-AS. The method further includes receiving, by the IMS-AS, a subscription request from HSS for one or more IP multimedia subsystem Data Channel (IMS DC) events associated with the IMS-AS. The method further includes detecting, by the IMS-AS, that the one or more IMS DC events occur at the IMS-AS. The method further includes transmitting, by the IMS-AS, the one or more notifications associated with the IMS DC events to at least one of the third party or network function and the HSS.

[0019] According to another embodiment of the present disclosure, a method for handling one or more notifications within an IP Multimedia Subsystem (IMS) architecture is disclosed herein. The method includes receiving, by a Home Subscriber Server (HSS), one or more IP Multimedia Subsystem Data Channel (IMS DC) events related subscription from a third party or network function for an IP Multimedia Public Identity (IMPU). The method further includes determining, by the HSS, whether one or more IMS DC services are enabled for the IMPU. The method further includes performing, by the HSS, one of, in response to determining that the one or more IMS DC services are enabled for the IMPU and the one or more IMS DC events are supported by the IMS AS, subscribing, on behalf of the third party or network function, for one or more IP Multimedia Subsystem Data Channel (IMS DC) events with an IMS Application Server (IMS-AS) by providing a notification end point address as of the HSS or third party, to handle one or more notifications associated with the IMS DC events from the IMS-AS; or in response to determining that the one or more IMS DC services are not enabled for the IMPU, not subscribing, on behalf of the third party or network function, for the one or more IMS DC events associated with the IMS-AS.

[0020] According to another embodiment of the present disclosure, a method for handling one or more notifications within an IP Multimedia Subsystem (IMS) architecture is disclosed herein. The method includes receiving, by a Data Channel Signaling Function (DCSF), a registration message from an IMS Application Server (IMS-AS), wherein the registration message comprises an IP Multimedia Public Identity (IMPU). The method further includes determining, upon receiving the registration message, by the DCSF, whether a plurality of conditions meets predefined criteria associated with the DCSF. The method further includes registering, by the DCSF, an address of the DCSF in a Home Subscriber Server (HSS) in response to determining that the plurality of conditions meets predefined criteria associated with the DCSF and upon receiving registration from the IMS AS. The method further includes receiving, by the DCSF, a subscription request from the HSS for one or more IP multimedia subsystem Data Channel (IMS DC) events associated with the DCSF. The method further includes detecting, by the DCSF, that the one or more IMS DC events occur at the DCSF. The method further includes transmitting, by the DCSF, the one or more notifications associated with the IMS DC events to at least one of the third party or network function and the HSS.

[0021] According to another embodiment of the present disclosure, a method for handling one or more notifications within an IP Multimedia Subsystem (IMS) architecture is disclosed herein. The method includes receiving, by a Home Subscriber Server (HSS), one or more IP Multimedia Subsystem Data Channel (IMS DC) events related subscription from a third party or network function for an IP Multimedia Public Identity (IMPU). The method further includes determining, by the HSS, whether one or more IMS DC services are enabled for the IMPU. The method further includes performing, by the HSS, one of, in response to determining that the one or more IMS DC services are enabled for the IMPU and the one or more IMS DC events are supported by a Data Channel Signaling Function (DCSF), subscribing, on behalf of the third party or network function, for one or more IP Multimedia Subsystem Data Channel (IMS DC) events with the DCSF by providing a notification end point address as of the HSS or third party, to handle one or more notifications associated with the IMS DC events from the DCSF; or in response to determining that the one or more IMS DC services are not enabled for the IMPU, not subscribing, on behalf of the third party or network function, for the one or more IMS DC events associated with the DCSF.

[0022] According to another embodiment of the present disclosure, an IMS Application Server (IMS-AS) for handling one or more notifications within an IP Multimedia Subsystem (IMS) architecture is disclosed herein. The IMS-AS includes a notification management module coupled with a memory, a processor, and a communicator. The notification management module is configured to receive a registration message from a Serving Call Session Control Function (S-CSCF), wherein the registration message comprises an IP Multimedia Public Identity (IMPU). The notification management module is further configured to determine, upon receiving the registration message a plurality of conditions that meet predefined criteria associated with the IMS-AS. The notification management module is further configured to register an address of the IMS-AS in a Home Subscriber Server (HSS) in response to determining that the plurality of conditions meets predefined criteria associated with the IMS-AS. The notification management module is further configured to receive a subscription request from HSS for one or more IP multimedia subsystem Data Channel (IMS DC) events associated with the IMS-AS. The notification management module is further configured to detect that the one or more IMS DC events occur at the IMS-AS. The notification management module is further configured to transmit the one or more notifications associated with the IMS DC events to at least one of the third party or network function and the HSS.

[0023] According to another embodiment of the present disclosure, a Home Subscriber Server (HSS) for handling one or more notifications within an IP Multimedia Subsystem (IMS) architecture is disclosed herein. The HSS includes a notification management module coupled with a memory, a processor, and a communicator. The notification management module is configured to receive one or more IP Multimedia Subsystem Data Channel (IMS DC) events related subscription from a third party or network function for an IP Multimedia Public Identity (IMPU). The notification management module is further configured to determine whether one or more IMS DC services are enabled for the IMPU. The notification management module is further configured to perform, one of, in response to determining that the one or more IMS DC services are enabled for the IMPU and the one or more IMS DC events are supported by the IMS AS, subscribing, on behalf of the third party or network function, for one or more IP Multimedia Subsystem Data Channel (IMS DC) events with an IMS Application Server (IMS-AS) by providing a notification end point address as of the HSS or third party, to handle one or more notifications associated with the IMS DC events from the IMS-AS; or in response to determining that the one or more IMS DC services are not enabled for the IMPU, not subscribing, on behalf of the third party or network function, for the one or more IMS DC events associated with the IMS-AS.

[0024] According to another embodiment of the present disclosure, a Data Channel Signaling Function (DCSF) for handling one or more notifications within an IP Multimedia Subsystem (IMS) architecture is disclosed herein. The DCSF includes a notification management module coupled with a memory, a processor, and a communicator. The notification management module is configured to receive a registration message from an IMS Application Server (IMS-AS), wherein the registration message comprises an IP Multimedia Public Identity (IMPU). The notification management module is further configured to determine, upon receiving the registration message, whether a plurality of conditions meets predefined criteria associated with the DCSF. The notification management module is further configured to register an address of the DCSF in a Home Subscriber Server (HSS) in response to determining that the plurality of conditions meets predefined criteria associated with the DCSF and upon receiving registration from the IMS AS. The notification management module is further configured to receive a subscription request from the HSS for one or more IP multimedia subsystem Data Channel (IMS DC) events associated with the DCSF. The notification management module is further configured to detect that the one or more IMS DC events occur at the DCSF. The notification management module is further configured to transmit the one or more notifications associated with the IMS DC events to at least one of the third party or network function and the HSS.

[0025] According to another embodiment of the present disclosure, a Home Subscriber Server (HSS) for handling one or more notifications within an IP Multimedia Subsystem (IMS) architecture is disclosed herein. The HSS includes a notification management module coupled with a memory, a processor, and a communicator. The notification management module is configured to receive one or more IP Multimedia Subsystem Data Channel (IMS DC) events related subscription from a third party or network function for an IP Multimedia Public Identity (IMPU). The notification management module is further configured to determine whether one or more IMS DC services are enabled for the IMPU. The notification management module is further configured to perform, one of, in response to determining that the one or more IMS DC services are enabled for the IMPU and the one or more IMS DC events are supported by a Data Channel Signaling Function (DCSF), subscribing, on behalf of the third party or network function, for one or more IP Multimedia Subsystem Data Channel (IMS DC) events with the DCSF by providing a notification end point address as of the HSS or third party, to handle one or more notifications associated with the IMS DC events from the DCSF; or in response to determining that the one or more IMS DC services are not enabled for the IMPU, not subscribing, on behalf of the third party or network function, for the one or more IMS DC events associated with the DCSF.To further clarify the advantages and features of the present invention, a more particular description of the invention will be rendered by reference to specific embodiments thereof, which are illustrated in the appended drawings. It is appreciated that these drawings depict only typical embodiments of the invention and are therefore not to be considered limiting of its scope. The invention will be described and explained with additional specificity and detail in the accompanying drawings.

[0026] The disclosed framework suggests that NF consumers establish subscriptions with a Home Subscriber Server (HSS), which will facilitate subscriptions to the IMS AS on their behalf

[0027] In addition, the disclosed method aims to address various challenges associated with the HSS-based subscription model, ensuring its effective implementation. Specifically, the disclosed method provides a robust framework that enables the IMS network to deliver event notifications related to an IMS Data Channel (DC) to third-party applications and network functions, thereby catering to individual subscribers or groups of subscribers.

[0028] These and other features, aspects, and advantages of the present invention will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:

[0029] FIGS. 1A-1Bare sequence flow diagrams illustrating a method for facilitating a subscription for a third party for one or more IMS DC events, according to an embodiment as disclosed herein;

[0030] FIG. 2illustrates a block diagram of an IMS Application Server (IMS-AS) for handling one or more notifications within an IMS architecture, according to an embodiment as disclosed herein;

[0031] FIG. 3illustrates a block diagram of a Home Subscriber Server (HSS) for handling the one or more notifications within the IMS architecture, according to an embodiment as disclosed herein;

[0032] FIG. 4illustrates a block diagram of a Data Channel Signaling Function (DCSF) for handling the one or more notifications within the IMS architecture, according to an embodiment as disclosed herein;

[0033] FIG. 5is a sequence flow diagram illustrating a method for IMS AS instance registration in the HSS within an IMS network, according to prior art;

[0034] FIGS. 6A-6Bare sequence flow diagrams illustrating a subscribe / notify method for subscriber-specific IMS events, according to an embodiment as disclosed herein;

[0035] FIG. 7is a flow diagram illustrating one or more operations performed by the IMS-AS for handling one or more notifications within the IMS architecture, according to an embodiment as disclosed herein;

[0036] FIG. 8is a flow diagram illustrating one or more operations performed by the HSS for handling one or more notifications within the IMS architecture, according to an embodiment as disclosed herein;

[0037] FIG. 9is a flow diagram illustrating one or more operations performed by a Data Channel Signaling Function (DCSF) for handling one or more notifications within the IMS architecture, according to an embodiment as disclosed herein; and

[0038] FIG. 10is a flow diagram illustrating one or more operations performed by the HSS for handling one or more notifications within the IMS architecture, according to another embodiment as disclosed herein.

[0039] Further, skilled artisans will appreciate that elements in the drawings are illustrated for simplicity and may not have necessarily been drawn to scale. For example, the flow charts illustrate the method in terms of the most prominent steps involved to help to improve understanding of aspects of the present invention. 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 embodiments of the present invention 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.

[0040] For the purpose of promoting an understanding of the principles of the invention, reference will now be made to the embodiment illustrated in the drawings and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended, such alterations and further modifications in the illustrated system, and such further applications of the principles of the invention as illustrated therein being contemplated as would normally occur to one skilled in the art to which the invention relates.

[0041] It will be understood by those skilled in the art that the foregoing general description and the following detailed description are explanatory of the invention and are not intended to be restrictive thereof.

[0042] Reference throughout this specification to "an aspect", "another aspect" or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrase "in an embodiment", "in one embodiment", "in another embodiment" and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.

[0043] The terms "comprise", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such process or method. Similarly, one or more devices or sub-systems or elements or structures or components proceeded by "comprises... a" does not, without more constraints, preclude the existence of other devices or other sub-systems or other elements or other structures or other components or additional devices or additional sub-systems or additional elements or additional structures or additional components.

[0044] 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. Also, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with one or more other embodiments to form new embodiments. The term "or" as used herein, refers to a non-exclusive or unless otherwise indicated. 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 skilled in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0045] As is traditional in the field, embodiments may be described and illustrated in terms of blocks that carry out a described function or functions. These blocks, which may be referred to herein as units or modules or the like, are physically implemented by analog or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware and software. 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 invention. Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the invention.

[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 alterations, equivalents, and substitutes in addition to those which are particularly set out in the accompanying drawings. Although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are generally only used to distinguish one element from another.

[0047] In one or more embodiments, the resolution of the critical issues related to IMS network capabilities will encompass several technical dimensions. First, a comprehensive analysis of the IMS architecture, interfaces, and operational procedures will be conducted to effectively expose the capabilities of the IMS network within specific scenarios related to IMS data channels, as discussed throughout the disclosure (FIGS. 1Ato10). This includes investigating the processes involved in the establishment, updating, and release of IMS data channels, as well as examining the mechanisms by which an application server can initiate requests to utilize the bootstrap data channel for downloading designated applications.

[0048] According to Technical Report (TR) 23.700-77, preliminary solutions have been proposed to meet the requirements for third-party Application Functions (AF) and Network Functions (NF) acting as consumers to subscribe to notifications from NF producers such as an IMS Application Servers (AS) and a Data Channel Service Function (DCSF), which pertain to events associated with IMS data channels. The disclosed framework suggests that NF consumers establish subscriptions with a Home Subscriber Server (HSS), which will facilitate subscriptions to the IMS AS on their behalf, as described in conjunction withFIGS. 1A-1B.

[0049] In addition, the disclosed method aims to address various challenges associated with the HSS-based subscription model, ensuring its effective implementation. Specifically, the disclosed method provides a robust framework that enables the IMS network to deliver event notifications related to an IMS Data Channel (DC) to third-party applications and network functions, thereby catering to individual subscribers or groups of subscribers.

[0050] For instance, consider a scenario associated with a real-world application of IMS network capabilities, a telecommunications provider has implemented an IMS architecture to support a range of services, including voice, video, and messaging. To enhance their offerings, the provider integrates smart home applications that utilize IMS data channels for real-time communication and notifications. In this scenario, a customer subscribes to a smart home service that enables control of devices such as lights, thermostats, and security cameras via a mobile application. Initially, when the customer installs a smart home application, a smart home application server requests the establishment of a bootstrap data channel with the IMS network to facilitate communication with IMS services. Subsequently, the smart home application server subscribes to the HSS to receive notifications regarding the customer's IMS data channel events, including device status updates. Upon receiving this subscription request, the HSS subscribes to the relevant IMS AS on behalf of the smart home application server.

[0051] Whenever an event occurs such as the customer activating the security system or adjusting the thermostat, the IMS AS sends an event notification to the HSS. The HSS then forwards these notifications to the smart home application server. For instance, if the customer sets the security camera to "active", the smart home application server receives this notification and updates the mobile app interface in real-time, enabling the customer to monitor the status of their devices instantly. This integration not only enhances the customer experience by providing real-time updates and control over their smart devices but also exemplifies the effective use of IMS architecture to facilitate communication between third-party applications and the IMS network. Ultimately, the telecommunications provider benefits by offering value-added services that increase customer engagement and satisfaction.

[0052] In the context of the third-party subscription mechanism for IMS DC events (e.g., session initiation, user registration, etc.), the TR 23.700-77 outlines a mechanism to fulfill the requirements for third-party entities, such as a Device Capability Application Server (DCAS), that seek to monitor IMS data channel-related events for specific subscribers (IMPU). In this context, the DCAS may initiate a discovery process to identify a Home Subscriber Server (HSS), which may subsequently establish subscriptions with the IMS AS and a Data Channel Signaling Function (DCSF) on behalf of the DCAS.

[0053] The existing framework detailed in the TR indicates that a Serving Call Session Control Function (S-CSCF) is configured to execute third-party registrations with the IMS AS. Following this, the IMS AS may register its address with the HSS. This process enables the HSS to recognize that DCAS has already subscribed to IMS data channel-related events for the specific IMPU, allowing the HSS to subsequently subscribe to the IMS AS on behalf of DCAS. However, it is important to note that the S-CSCF may perform third-party registrations with multiple IMS AS instances, such as a SCC-AS, which facilitates Single Radio Voice Call Continuity (SRVCC) features and IP-SM-GW which facilitates IMS based messaging features. These specific IMS AS instances are not required to register their addresses with the HSS for IMS DC functionalities, as these constitute supplementary signaling and add unnecessary loads on the network systems.

[0054] To streamline this process, the disclosed method suggests that the IMS AS, upon receiving third-party registration from the S-CSCF, should only register its address with the HSS if it possesses the capability to support IMS DC. Additionally, there may be instances where an IMS AS is capable of supporting IMS DC features, but the corresponding IMPU does not have IMS DC services enabled in the HSS / UDM. Therefore, the disclosed method suggests that when the IMS AS, which supports IMS DC, receives subscription information from the HSS / UDM and determines that IMS DC is not enabled for the IMPU, then it should refrain from registering its address with the HSS. This is due to the fact that the IMPU would be unable to establish a successful IMS DC session.

[0055] In one or more embodiments, the disclosed method suggests that if the HSS receives an IMS DC-related subscription request from the third party (e.g., DCAS) for a specific IMPU, and subsequently finds that IMS DC is not enabled for that IMPU, the HSS should refrain from subscribing to the IMS AS on behalf of the third party (e.g., DCAS).

[0056] In one or more embodiments, if certain IMS DC-related services are provided by the DCSF in addition to the IMS AS, the HSS must also subscribe to the DCSF on behalf of the third party (e.g., DCAS). However, since the HSS lacks awareness of which DCAS is managing the IMPU, it cannot subscribe to a specific DCAS. Therefore, the disclosed method suggests that upon receiving third-party registration from the S-CSCF, if the IMS AS confirms its capability to support IMS data channel and verifies that IMS DC is enabled in the HSS / UDM for the IMPU, it may also send a registration request to the DCSF. Following this, the DCSF may register its address with the HSS, allowing the HSS to subscribe to IMS DC events on behalf of the third party (e.g., DCAS).

[0057] In one or more embodiments, upon the occurrence of an event at the IMS AS, the disclosed method suggests that the IMS AS may notify the HSS if the HSS has provided its own address in a notification target. Subsequently, the HSS may forward this notification to the third party (e.g., DCAS). To optimize event notifications directly to an NF consumer, the HSS may include the third-party (e.g., DCAS) address in the notification target. Based on this address, the IMS AS may directly send notifications or notification reports to the third party (e.g., DCAS).

[0058] In one or more embodiments, similarly, when an event occurs at the DCSF, the disclosed method suggests that the DCSF may notify the HSS if the HSS has designated its address in the notification target. The HSS may then forward this notification to the third party (e.g., DCAS). To enhance the efficiency of event notifications directly to the NF consumer, the HSS may provide the third-party (e.g., DCAS) address in the notification target, allowing the DCSF to send notifications or notification reports directly to the third party (e.g., DCAS).

[0059] Referring now to the drawings, and more particularly toFIGS. 1Ato10, where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.

[0060] FIGS. 1A-1Bare sequence flow diagrams illustrating a method 10 for facilitating a subscription for a third party for one or more IMS DC events, according to an embodiment as disclosed herein. The sequence flow diagrams include several operations outlined as follows, wherein the several operations are performed by the several network entities. Examples of the several network entities may include an IMS Application Server (IMS-AS) 100, a Home Subscriber Server (HSS) 200, a Serving Call Session Control Function (S-CSCF) 300, and a Data Channel Signalling Function (DCSF) 400.

[0061] At operation101, the method 10 includes processing, by the HSS 200, a subscription request for one or more Initial Mobile Public User Identifiers (IMPU) related to one or more IMS DC events from a third party or Data Communication Application Server (DCAS). If the DCSF 400 is interested in these one or more IMS DC events, the DCSF 400 may also establish a subscription with the HSS 200, similar to a DCAS process.

[0062] At operation102, the method 10 includes performing a third-party registration, by the S-CSCF 300, with the IMS-AS 100 based on an initial filter criterion (iFC). A Multimedia Telephony Application Server (MMTEL AS) can be enhanced to support IMS DC functionality, or a new standalone IMS AS may be deployed that inherently supports IMS DC. In either scenario, the same IMS AS address can be configured as part of the iFC. It is crucial for the S-CSCF300to verify whether the IMS DC is enabled for the specified IMPU; the third-party registration may only be initiated if the IMS DC is confirmed as enabled. This verification requires checking the subscriber data before proceeding with the third-party registration.

[0063] At operation103, the method 10 includes performing one or more operations. For instance, once the IMS-AS 100 retrieves the subscriber data, the IMS-AS 100 may confirm the enablement of IMS DC for the subscriber. At operation104, the method 10 includes registering, by the IMS-AS 100, its address with the HSS200. At operation105, the method 10 includes evaluating, by the HSS 200, whether IMS DC is enabled for the IMPU. If it is, the HSS 200 subscribes to IMS DC-related events as supported by the IMS-AS 100. The HSS 200 may retain its address within the notification target to receive event notifications or provide the address of the third party / DCAS, allowing the IMS-AS 100 to send notifications directly to the third party / DCAS.

[0064] At operation106, the method 10 includes forwarding, by the IMS-AS 100, upon receiving the third-party registration from the S-CSCF 300, this registration to the DCSF 400. The S-CSCF 300 may have a DCSF address locally configured for each IMPU or utilize a Network Function Repository (NRF) to dynamically discover the DCSF address. At operations107-108, the method 10 includes registering, by the DCSF 400, its address with the HSS 200, which checks if IMS DC is enabled for the IMPU. If confirmed, the HSS 200 subscribes to IMS DC-related events supported by the DCSF 400, similarly retaining its address in the notification target or providing the third party / DCAS address for direct notifications from the DCSF 400.

[0065] At operations109,110, and111, the method 10 includes performing one or more operations at the S-CSCF 300. For instance, as users initiate, update, or release IMS DC-related events, both the IMS AS 100 and the DCSF 400 monitor these IMS DC-related events.

[0066] At operation112, the method 10 includes sending, based on the IMS DC-related events, by the IMS AS 100, one or more notifications to the designated notification target address, the HSS 200may receive these notifications and relay them to the third party / DCAS if the address belongs to the HSS. At operation113, the method 10 includes sending, based on the IMS DC-related events, by the DCSF 400, following a similar process, one or more notifications to the specified notification target address, with the HSS 200 again acting as an intermediary if necessary.

[0067] For instance, consider an example scenario for a smart home monitoring system, various devices such as cameras, sensors, and alarms communicate over the IMS network, allowing users to receive notifications about events like motion detection or door openings through a third-party application called "home network" The process begins when the HSS 200 receives a subscription from the "home network" for a list of IMPU related to the smart home devices. Recognizing the value of these updates, the DCSF 400 also subscribes to the same IMPU with the HSS 200, establishing a shared interest in the events. Next, the S-CSCF 300 steps in to facilitate third-party registration with the IMS AS 100 based on the iFC relevant to the "home network". This registration is crucial, as it allows the "home network" to receive notifications about the smart home events. Simultaneously, the MMTEL AS has been enhanced to support the IMS DC, ensuring that it can handle the necessary data for these devices.

[0068] To ensure proper functionality, the S-CSCF 300 checks if the IMS DC is enabled for the specific IMPU associated with the user's smart home devices. If the check confirms that IMS DC is enabled, the S-CSCF 300 proceeds with the third-party registration, thereby allowing the "home network" to receive timely notifications. Once the registration is complete, the IMS AS 100 verifies that IMS DC is enabled for the subscriber. In response, it registers its address with the HSS 200, establishing a direct line for notifications. The HSS 200 then confirms the IMS DC status for the IMPU and subscribes to the relevant IMS DC events supported by the IMS AS 100. At this point, the HSS 200 can either keep its address as the notification target or provide the third-party address for direct notifications. Following this, the IMS AS 100, having received the third-party registration from the S-CSCF 300, forwards this registration to the DCSF 400. The DCSF 400, recognizing the importance of these updates, registers its address with the HSS 200 to ensure it can also receive event notifications. The HSS 200 checks the IMS DC status for the DCSF 400 and subscribes to the corresponding events, further strengthening the network of communication.

[0069] As users interact with their smart home system turning on cameras, updating settings, or releasing alarms, the IMS AS 100 and DCSF 400 continuously observe these IMS DC-related events. The IMS AS 100 then sends notifications to the configured notification target, which could be the HSS 200 or directly to the "home network". If the target is the HSS 200, it efficiently forwards the notifications to the "home network", ensuring that users are kept informed. Similarly, the DCSF 400 sends notifications to its designated target, maintaining the flow of information.

[0070] FIG. 2illustrates a block diagram of the IMS-AS 100 for handling one or more notifications within an IMS architecture, according to an embodiment as disclosed herein.

[0071] In one or more embodiments, the IMS-AS 100 comprises a system 101. The system 101 may include a memory 110, a processor 120, a communicator 130, and a notification management module 140. In one or more embodiments, the system 101 may be implemented on one or multiple electronic devices (not shown in FIG. 2).

[0072] In an embodiment, the memory 110 stores instructions to be executed by the processor 120 for handling one or more notifications within the IMS architecture, as discussed throughout the disclosure. The memory 110 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 110 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 110 is non-movable. In some examples, the memory 110 can be configured to store larger amounts of information than the memory. 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). The memory 110 can be an internal storage unit, or it can be an external storage unit of the IMS-AS 100, a cloud storage, or any other type of external storage.

[0073] The processor 120 communicates with the memory 110, the communicator 130, and the notification management module 140. The processor 120 is configured to execute instructions stored in the memory 110 and to perform various processes for handling the one or more notifications within the IMS architecture, as discussed throughout the disclosure. The processor 120 may include one or a plurality of processors, maybe 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 Artificial intelligence (AI) dedicated processor such as a Neural Processing Unit (NPU).

[0074] The communicator 130 is configured for communicating internally between internal hardware components and with external devices (e.g., server) via one or more networks (e.g., radio technology). The communicator 130 includes an electronic circuit specific to a standard that enables wired or wireless communication.

[0075] In one or more embodiments, the notification management module 140 is implemented by processing circuitry such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by 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.

[0076] In one or more embodiments, the notification management module 140 is configured to receive a registration message from the S-CSCF 300. The registration message may include, for example, but is not limited to, an IP Multimedia Public Identity (IMPU). The IMPU is a unique identifier assigned to a user in the IMS architecture when a User Equipment (UE) initiates registration with at least one of the S-CSCF 300.

[0077] In one or more embodiments, the notification management module 140 is configured to determine, upon receiving the registration message, whether a plurality of conditions meets predefined criteria associated with the IMS-AS 100. Examples of the plurality of conditions may include, but is not limited to, (a) determining whether the IMS-AS 100 is capable of supporting one or more IMS-DC features; (b) determining whether a user subscription status is authorized and enabled to use one or more IMS DC services; (c) determining whether the one or more IMS DC services are enabled for the received IMPU in the HSS or Unified Data Management (UDM). The notification management module 140 is further configured to register an address of the IMS-AS 100 in the HSS 200 in response to determining that the plurality of conditions meets predefined criteria associated with the IMS-AS 100.

[0078] For instance, consider an example scenario where a telecommunication provider launches one or more Voice over LTE (VoLTE) services, the integration of the IMS-AS 100 is crucial for managing multimedia sessions. Before registering the IMS-AS 100 in the HSS 200, several conditions must be assessed to ensure seamless service delivery. First, network engineers evaluate the IMS-AS's capability to support essential one or more VoLTE features, such as call continuity, emergency calling, and HD voice, by conducting diagnostic tests to confirm that the software is updated and properly configured. Next, the telecommunication provider reviews user subscriptions to ensure customers have plans that include one or more VoLTE services, accessing the HSS 200 to verify that user accounts are authorized for these one or more VoLTE services without any restrictions. Finally, the network engineers check the HSS 200 to confirm that the necessary IMS-DC events / services, such as call setup and media handling, are activated for the users' IMPU. Once all conditions are verified and confirmed, the telecommunications provider registers the IMS-AS address in the HSS 200, enabling the IMS-AS 100 to effectively manage VoLTE sessions and ensuring that users can make high-quality voice calls over a LTE network.

[0079] In one or more embodiments, the notification management module 140 is further configured to receive a subscription request from the HSS 200 for one or more IMS DC events associated with the IMS-AS 100. The notification management module 140 is further configured to detect that the one or more IMS DC events occur at the IMS-AS.

[0080] In one or more embodiments, the notification management module 140 is further configured to transmit the one or more notifications associated with the IMS DC events to at least one of the third party or network functions and the HSS 200 by performing one of, (a) transmitting the one or more notifications to the HSS 200, wherein the HSS 200 subsequently forwards the one or more notifications to at least one of the third party or network function; or (b) transmitting the one or more notifications directly to at least one of the third party or network function, bypassing the HSS 200.

[0081] AlthoughFIG. 2shows various hardware components of the IMS-AS 100, but it is to be understood that other embodiments are not limited thereon. In other embodiments, the IMS-AS 100 may include less or more number of components. Further, the labels or names of the components are used only for illustrative purposes and do not limit the scope of the invention. One or more components can be combined to perform the same or substantially similar functions for handling the one or more notifications within the IMS architecture.

[0082] FIG. 3illustrates a block diagram of the HSS 200 for handling the one or more notifications within the IMS architecture, according to an embodiment as disclosed herein.

[0083] In one or more embodiments, the HSS 200 comprises a system 201. The system 201 may include a memory 210, a processor 220, a communicator 230, and a notification management module 240. In one or more embodiments, the system 201 may be implemented on one or multiple electronic devices (not shown in FIG. 3) and one or more fundamental functionalities related to the memory 210, the processor 220, and the communicator 230 are identical to those described in FIG. 2 and are omitted herein for the sake of brevity.

[0084] In one or more embodiments, the notification management module 240 is implemented by processing circuitry such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by 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.

[0085] In one or more embodiments, the notification management module 240 is configured to receive the one or more IMS DC events related subscription from the third party or network function for the IMPU. The notification management module 240 is further configured to determine whether one or more IMS DC services are enabled for the IMPU. The notification management module 240 is further configured to perform one of the following:

[0086] Subscribing, on behalf of the third party or network function, for one or more IMS DC events with the IMS-AS 100 by providing a notification end point address as of the HSS 200 or third party, to handle one or more notifications associated with the IMS DC events from the IMS-AS 100, in response to determining that the one or more IMS DC services are enabled for the IMPU and the one or more IMS DC events are supported by the IMS AS 100.

[0087] Not subscribing, on behalf of the third party or network function, for the one or more IMS DC events associated with the IMS-AS 100, in response to determining that the one or more IMS DC services are not enabled for the IMPU.

[0088] In one or more embodiments, the notification management module 240 is configured to receive, after subscribing, the one or more notifications associated with the IMS DC events from the IMS-AS 100. The HSS 200 subsequently forwards the one or more notifications to at least one of the third party or network function.

[0089] In one or more embodiments, the notification management module 240 is further configured to perform one of the following:

[0090] Subscribing, on behalf of the third party or network function, for one or more IMS DC events with the DCSF 400 by providing a notification end point address as of the HSS 200 or third party, to handle one or more notifications associated with the IMS DC events from the DCSF 400, in response to determining that the one or more IMS DC services are enabled for the IMPU and the one or more IMS DC events are supported by the DCSF 400.

[0091] Not subscribing, on behalf of the third party or network function, for the one or more IMS DC events associated with the DCSF 400, in response to determining that the one or more IMS DC services are not enabled for the IMPU.

[0092] In one or more embodiments, the notification management module 240 is configured to receive, after subscribing, the one or more notifications associated with the IMS DC events from the DCSF 400. The HSS 200 subsequently forwards the one or more notifications to at least one of the third party or network functions.

[0093] AlthoughFIG. 3shows various hardware components of the HSS 200, but it is to be understood that other embodiments are not limited thereon. In other embodiments, the HSS 200 may include less or more number of components. Further, the labels or names of the components are used only for illustrative purposes and do not limit the scope of the invention. One or more components can be combined to perform the same or substantially similar functions for handling the one or more notifications within the IMS architecture.

[0094] FIG. 4illustrates a block diagram of the DCSF 400 for handling the one or more notifications within the IMS architecture, according to an embodiment as disclosed herein.

[0095] In one or more embodiments, the DCSF 400 comprises a system 401. The system 401 may include a memory 410, a processor 420, a communicator 430, and a notification management module 440. In one or more embodiments, the system 401 may be implemented on one or multiple electronic devices (not shown in FIG. 4) and one or more fundamental functionalities related to the memory 410, the processor 420, and the communicator 430 are identical to those described in FIG. 2 and omitted herein for the sake of brevity.

[0096] In one or more embodiments, the notification management module 440 is implemented by processing circuitry such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by 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.

[0097] In one or more embodiments, the notification management module 440 is configured to receive a registration message from the IMS-AS 100. The registration message may include, for example, but is not limited to the IMPU. The notification management module 440 is configured to determine, upon receiving the registration message, whether the plurality of conditions meets predefined criteria associated with the DCSF 400. Examples of the plurality of conditions may include, but is not limited to, (a) determine whether the DCSF 400 is capable of supporting one or more IMS-DC features; (b) determine whether the one or more IMS DC services are enabled for the received IMPU in the HSS 200 or the UDM.

[0098] In one or more embodiments, the notification management module 440 is further configured to register an address of the DCSF 400 in the HSS 200 in response to determining that the plurality of conditions meets predefined criteria associated with the DCSF 400 and upon receiving registration from the IMS AS 100. The notification management module 440 is further configured to receive a subscription request from the HSS for one or more IMS DC events associated with the DCSF 400. The notification management module 440 is further configured to detect that the one or more IMS DC events occur at the DCSF.

[0099] The notification management module 440 is further configured to transmit the one or more notifications associated with the IMS DC events to at least one of the third party or network functions and the HSS 200 by performing one of the following:

[0100] Transmitting the one or more notifications to the HSS 200, wherein the HSS subsequently forwards the one or more notifications to at least one of the third party or network function;

[0101] Transmitting the one or more notifications directly to at least one of the third party or network function, bypassing the HSS 200.

[0102] AlthoughFIG. 4shows various hardware components of the DCSF 400, but it is to be understood that other embodiments are not limited thereon. In other embodiments, the DCSF 400 may include less or more number of components. Further, the labels or names of the components are used only for illustrative purposes and do not limit the scope of the invention. One or more components can be combined to perform the same or substantially similar functions for handling the one or more notifications within the IMS architecture.

[0103] FIG. 5is a sequence flow diagram illustrating a method 500 for IMS AS instance registration in the HSS 200 within the IMS network (IMS architecture), according to prior art.

[0104] The IMS network may include several components that facilitate the delivery of multimedia services over IP networks. These components may include a Proxy Call Session Control Function (P-CSCF) 300a, an Interrogating / Serving Call Session Control Function (I / S-CSCF) 300b, the IMS AS 100, the HSS 200, and a User Equipment (UE) 501. The P-CSCF 300a is configured to serve as an initial point of contact for the UE 501 within the IMS architecture. It acts as a proxy for SIP signaling, providing functionalities such as request routing, security, and session management. The P-CSCF 300a is configured to ensure that signaling messages are appropriately directed to the relevant CSCF and also manages the interaction with the UE 501. The I / S-CSCF plays a pivotal role in the registration and session management processes. The I / S-CSCF is configured to interrogate the HSS 200 to retrieve subscriber information and for routing incoming SIP requests to the appropriate S-CSCF 300b. The S-CSCF 300b then manages the session control and service execution. The IMS AS 100 is configured to provide one or more application-level services to the IMS network. The IMS AS 100 is configured to execute service logic and manage user interactions with multimedia services. The IMS AS 100 interfaces with the S-CSCF 300b to receive session requests and provide the necessary service capabilities, such as voice, video, and messaging. The HSS 200 is a centralized database that contains subscriber profiles, authentication credentials, and service information. It plays a crucial role in user authentication, authorization, and service provisioning. The HSS 200 interacts with various components in the IMS architecture to ensure that the necessary subscriber data is accessible for session establishment and service delivery.

[0105] The sequence flow diagrams include several operations outlined as follows. At operation502, the method 500 includes initiating, by a User Equipment (UE) 400, an initial registration process within the IMS network. In other words, the UE may transmit a registration request to the S-CSCF 300b. At operation503, the method 500 includes proceeding, by the S-CSCF 300b, upon receiving the registration request from the UE 400, to perform the third-party registration with the IMS AS 100 that has been designated for the registering UE 400. This registration is crucial for establishing the communication context and ensuring that the IMS AS 100 can manage the services associated with the UE 501. At operation504, the method 500 includes registering, by the IMS AS 100 assigned to the specific UE or its associated Identity (IMPU) subsequently, with the HSS 200. This registration is executed using a Nhss_ImsUECM_Registration service operation or through an "Sh" interface. This interaction ensures that the HSS 200 has up-to-date information regarding the UE's registration status and associated service capabilities.

[0106] FIGS. 6A-6Bare sequence flow diagrams illustrating a subscribe / notify method 600 for subscriber-specific IMS events, according to an embodiment as disclosed herein. The sequence flow diagrams include several operations outlined as follows.

[0107] At operation601, the method 600 includes performing, by the UE 501, an initial registration within the IMS network / architecture. This registration establishes a presence of the UE 501 in the IMS network, enabling participation in one or more IMS services. At operation602, the method 600 includes initiating, by an Application Function (AF) 600b, a subscription request to a Network Exposure Function (NEF) 600a using a Nnef_imsEE_Subscribe operation, which may include one or more IMS subscriber IDs to indicate specific events of interest.

[0108] At operation603, the method 600 includes processing, by the NEF 600a, upon receiving the subscription request, each IMS subscriber ID, and generating individual subscription requests to the HSS 200 using an Nhss_ImsEE_Subscribe service operation. During this operation, the NEF 600a constructs a notification target address and a notification correlation ID, essential for tracking notifications related to the subscription. At operation604, the method 600 includes responding, by the NEF 600a, after initiating these requests (503), the NEF 600a responds to the AF 600b with an Nnef_ImsEE_Subscribe response, confirming a receipt and processing of the subscription.

[0109] At operation605, the method 600 includes locating, by the HSS 200, an appropriate IMS AS instance, which may relate to IMS AS 100, serving the UE 501 based on a registration information established earlier. It verifies whether the identified IMS AS instance associated with the IMS subscriber (IMPU) supports the requested IMS event by referencing an NF profile stored in a Network Repository Function (NRF). If the UE 501 is not registered in the IMS 100, the HSS bypasses the subsequent steps (506 and 507) and retains the event subscription request associated with the IMPU.

[0110] If the UE 501 is not IMS registered as in operation 501, then the HSS 200 may store the event subscription request per IMPU.

[0111] At operation606, the method 600 includes subscribing, by the HSS 200, the identified IMS AS instance to the requested IMS event using an Nimsas_ImsEE_Subscribe request, which includes the IMPU and the NEF address designated as the notification endpoint. Alternatively, the HSS 200 may utilize the "Sh" interface to relay the event subscription directly to the IMS AS instance assigned to the UE 501. At operation607, the method 600 includes acknowledging, by the IMS AS 100, the subscription request by returning a Nimsas_ImsEE_Subscribe response to the HSS 200, confirming the successful establishment of the subscription. At operation608, the method 600 includes transmitting / forwarding the Nhss_ImsEE_subscribe response back to the NEF 600a, indicating the outcome of the subscription process.

[0112] At operation609, at a later point, the method 600 includes detecting, by the IMS AS 100, an occurrence of the requested event pertaining to the UE 501. At operation610, following this detection, the method 600 includes transmitting, by the IMS AS 100, an Nimsas_ImsEE_Notify request to the NEF 600a, signaling that the event has been triggered. At operation611, the method 600 includes processing, by the NEF 600a, this receives notification and responds to the IMS AS 100 with a Nimsas_ImsEE_Notify Response, acknowledging receipt of the notification.

[0113] At operation612, the method 600 includes mapping, by the NEF 600a, a notification correlation ID received earlier to the corresponding subscription record within the NEF. Using this mapping, the NEF dispatches a Nnef_ImsEE_Notify request to the AF 600b, utilizing the previously established notification target address and notification correlation ID. At operation613, the method 600 includes transmitting, by the AF 600b, an Nnef_ImsEE_Notify Response back to the NEF 600a, completing the notify procedure, and confirming the successful delivery of the event notification.

[0114] FIG. 7is a flow diagram illustrating one or more operations performed by the IMS-AS 100 for handling the one or more notifications within the IMS architecture, according to an embodiment as disclosed herein. The flow diagram includes several operations outlined as follows.

[0115] At operation701, a method 700 includes receiving the registration message from the S-CSCF 300, where the registration message comprises the IMPU. At operation702, the method 700 includes determining whether the plurality of conditions meets predefined criteria associated with the IMS-AS 100. At operation703, the method 700 includes registering the address of the IMS-AS 100 in the HSS 200 in response to determining that the plurality of conditions meets predefined criteria associated with the IMS-AS 100. Examples of the plurality of conditions may include, but is not limited to, (a) determining whether the IMS-AS 100 is capable of supporting one or more IMS-DC features; (b) determining whether a user subscription status is authorized and enabled to use one or more IMS DC services; (c) determining whether the one or more IMS DC services are enabled for the received IMPU in the HSS or UDM. At operation704, the method 700 includesreceiving the subscription request from the HSS 200 for one or more IMS DC events associated with the IMS-AS 100. At operation705, the method 700 includes detecting that the one or more IMS DC events occur at the IMS-AS 100. At operation706, the method 700 includes transmitting the one or more notifications associated with the IMS DC events to at least one of the third party or network function and the HSS 200. Further, a detailed description related to the various operations ofFIG. 7is covered in the description related toFIG. 1AtoFIG. 6B, and is omitted herein for the sake of brevity.

[0116] FIG. 8is a flow diagram illustrating one or more operations performed by the HSS 800 for handling one or more notifications within the IMS architecture, according to an embodiment as disclosed herein. The flow diagram includes several operations outlined as follows.

[0117] At operation801, a method 800 includes receiving the one or more IMS DC events related subscription from a third party or network function for the IMPU. At operation802, the method 800 includes determining whether one or more IMS DC services are enabled for the IMPU and IMS DC events supported by the IMS AS 100.

[0118] At operation803, the method 800 includes subscribing, on behalf of the third party or network function, for one or more IMS DC events with the IMS-AS 100 by providing the notification end point address as of the HSS 200 or third party, to handle one or more notifications associated with the IMS DC events from the IMS-AS 100, in response to determining that the one or more IMS DC services are enabled for the IMPU and the one or more IMS DC events are supported by the IMS AS. At operation804, the method 800 includes not subscribing, on behalf of the third party or network function, for the one or more IMS DC events associated with the IMS-AS 100, in response to determining that the one or more IMS DC services are not enabled for the IMPU. Further, a detailed description related to the various operations ofFIG. 8is covered in the description related toFIG. 1AtoFIG. 6B, and is omitted herein for the sake of brevity.

[0119] FIG. 9is a flow diagram illustrating one or more operations performed by the DCSF 400 for handling the one or more notifications within the IMS architecture, according to an embodiment as disclosed herein. The flow diagram includes several operations outlined as follows.

[0120] At operation901, a method 900 includes receiving the registration message from the IMS-AS 100, where the registration message comprises the IMPU. At operation902, the method 900 includes determining whether the plurality of conditions meets predefined criteria associated with the DCSF 400. Examples of the plurality of conditions may include, but is not limited to, (a) determining whether the DCSF 400 is capable of supporting one or more IMS-DC features; (b) determining whether a user subscription status is authorized and enabled to use one or more IMS DC services; (c) determining whether the one or more IMS DC services are enabled for the received IMPU in the HSS or UDM. At operation903, the method 900 includes registering the address of the DCSF 400 in the HSS 200 in response to determining that the plurality of conditions meets predefined criteria associated with the DCSF 400. At operation904, the method 900 includes receiving the subscription request from the HSS 200 for one or more IMS DC events associated with the DCSF 400. At operation905, the method 900 includes detecting that the one or more IMS DC events occur at the DCSF 400. At operation906, the method 900 includes transmitting the one or more notifications associated with the IMS DC events to at least one of the third party or network function and the HSS 200. Further, a detailed description related to the various operations ofFIG. 9is covered in the description related toFIG. 1AtoFIG. 6B, and is omitted herein for the sake of brevity.

[0121] FIG. 10is a flow diagram illustrating one or more operations performed by the HSS 200 for handling one or more notifications within the IMS architecture, according to another embodiment as disclosed herein. The flow diagram includes several operations outlined as follows.

[0122] At operation1001, a method 1000 includes receiving the one or more IMS DC events related subscription from a third party or network function for the IMPU. At operation1002, the method 1000 includes determining whether one or more IMS DC services are enabled for the IMPU and IMS DC events supported by the IMS AS 100.

[0123] At operation1003, the method 1000 includes subscribing, on behalf of the third party or network function, for one or more IMS DC events with the DCSF 400 by providing the notification end point address as of the HSS 200 or third party, to handle one or more notifications associated with the IMS DC events from the DCSF 400, in response to determining that the one or more IMS DC services are enabled for the IMPU and the one or more IMS DC events are supported by the DCSF 400. At operation1004, the method 1000 includes not subscribing, on behalf of the third party or network function, for the one or more IMS DC events associated with the DCSF 400, in response to determining that the one or more IMS DC services are not enabled for the IMPU. Further, a detailed description related to the various operations ofFIG. 10is covered in the description related toFIG. 1AtoFIG. 6B, and is omitted herein for the sake of brevity.

[0124] The disclosed method has several advantages over the existing method, which are stated below.

[0125] a.Enhanced security: the disclosed method validates the user's subscription status before registration, to ensure that only authorized users can access IMS DC services, reducing unauthorized access.

[0126] b.Selective registration: The IMS AS 100 registers its address in the HSS 200 only for users authorized to use IMS DC, minimizing unnecessary resource allocation and network traffic.

[0127] c.Improved performance: by selective registrations to authorized users, the load on the HSS 200 is reduced, leading to faster processing times and improved overall system performance. In addition, the HSS 200 subscribes on behalf of third parties for IMS DC events only when the user's subscription status is enabled.

[0128] d.Enhanced notifications: The IMS AS 100 to directly notify third parties bypassing HSS streamlines communication, reducing latency and improving response times.

[0129] e.Lower operational costs: By selective registration and enhanced notification processes, operational costs related to data handling and server management can be significantly lowered.

[0130] The various actions, acts, blocks, steps, or the like in the flow diagrams 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.

[0131] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one ordinary skilled in the art to which this invention belongs. The system, methods, and examples provided herein are illustrative only and not intended to be limiting.

[0132] While specific language has been used to describe the present subject matter, any limitations arising on account thereto, are not intended. As would be apparent to a person in the art, various working modifications may be made to the method to implement the inventive concept as taught herein. The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment.

[0133] The embodiments disclosed herein can be implemented using at least one hardware device and performing network management functions to control the elements.

[0134] 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 preferred embodiments, 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 an IP Multimedia Subsystem Application Server (IMS-AS), for an IP Multimedia Subsystem (IMS) architecture, the method comprising:receiving a registration message from a Serving Call Session Control Function (S-CSCF),registering an address of the IMS-AS in a Home Subscriber Server (HSS), wherein the IMS-AS supports monitoring of one or more IP multimedia subsystem Data Channel (IMS DC) events;receiving a subscription request from the HSS for one or more subscriber specific IMS DC events associated with the IMS-AS;detecting that a subscriber specific IMS DC event occurs; andtransmitting, to a network function, a notification associated with the subscriber specific IMS DC event.2.The method of claim 1, wherein transmitting, to the network function, the notification associated with the subscriber specific IMS DC event comprises:performing one of:transmitting the notification to the network function via HSS; ortransmitting the notification directly to the network function.3.The method of claim 1, wherein the subscription request is received from the HSS for the one or more subscriber specific IMS DC events associated with the IMS-AS, based on an IMS DC being enabled for an IMS public identity (IMPU) and the one or more subscriber specific IMS DC events being supported by the IMS AS.4.The method of claim 1, wherein the registration message comprises an IMPU, wherein the IMPU is a unique identifier assigned to a user in the IMS architecture when a User Equipment (UE) initiates registration with at least one of the S-CSCF.5.A method performed by a Home Subscriber Server (HSS) for an IP Multimedia Subsystem (IMS) architecture, the method comprising:receiving, from a network function, a subscription request related to one or more subscriber specific IP Multimedia Subsystem Data Channel (IMS DC) events for an IP Multimedia Public Identity (IMPU);determining whether an IMS DC is enabled for the IMPU and whether the one or more subscriber specific IMS DC events related to the subscription request are supported by an IMS Application Server (IMS-AS); andsubscribing for the one or more subscriber specific IMS DC events related to the subscription request to the IMS-AS, in response to determining that the IMS DC is enabled for the IMPU and the one or more subscriber specific IMS DC events related to the subscription request are supported by the IMS AS.6.The method of claim 5, further comprising:receiving, from the IMS-AS, a notification associated with a subscriber specific IMS DC event,transmitting the notification to the network function.7.The method of claim 5, wherein an address of the IMS-AS is registered in a HSS, wherein the IMS-AS supports monitoring of one or more IMS DC events.8.The method of claim 5, wherein the IMPU is a unique identifier assigned to a user in the IMS architecture when a User Equipment (UE) initiates registration with at least one of the Serving Call Session Control Function (S-CSCF).9.An IP Multimedia Subsystem Application Server (IMS-AS) within an IP Multimedia Subsystem (IMS) architecture, the IMS-AS comprising:a memory;a processor;a communicator; anda notification management module, operably connected to the memory, the processor, and the communicator, the notification management module is configured to:receive a registration message from a Serving Call Session Control Function (S-CSCF);register an address of the IMS-AS in a Home Subscriber Server (HSS), wherein the IMS-AS supports monitoring of one or more IP multimedia subsystem Data Channel (IMS DC) events;receive a subscription request from the HSS for one or more subscriber specific IMS DC events associated with the IMS-AS;detect that a subscriber specific IMS DC event occurs; andtransmit, to a network function, a notification associated with the subscriber specific IMS DC event.10.The IMS-AS of claim 9, wherein to transmit, to the network function, the notification associated with the subscriber specific IMS DC event, the notification management module is configured to:perform one of:transmitting the notification to the network function via HSS; ortransmitting the notification directly to the network function.11.The IMS-AS of claim 9, wherein the subscription request is received from the HSS for the one or more subscriber specific IMS DC events associated with the IMS-AS, based on an IMS DC being enabled for an IMS public identity (IMPU) and the one or more subscriber specific IMS DC events being supported by the IMS AS.12.The IMS-AS of claim 9, wherein the registration message comprises an IMPU, wherein the IMPU is a unique identifier assigned to a user in the IMS architecture when a User Equipment (UE) initiates registration with at least one of the S-CSCF.13.A Home Subscriber Server (HSS) for an IP Multimedia Subsystem (IMS) architecture, the HSS comprising:a memory;a processor;a communicator; anda notification management module, operably connected to the memory, the processor, and the communicator, the notification management module is configured to:receive, from a network function, a subscription request related to one or more subscriber specific IP Multimedia Subsystem Data Channel (IMS DC) events for an IP Multimedia Public Identity (IMPU);determine whether an IMS DC is enabled for the IMPU and whether the one or more subscriber specific IMS DC events related to the subscription request are supported by an IMS Application Server (IMS-AS); andsubscribe for the one or more subscriber specific IMS DC events related to the subscription request to the IMS-AS, in response to determining that the IMS DC is enabled for the IMPU and the one or more subscriber specific IMS DC events related to the subscription request are supported by the IMS AS.14.The HSS of claim 13, wherein the notification management module is further configured to:receive, from the IMS-AS, a notification associated with a subscriber specific IMS DC event,transmit the notification to the network function.15.The HSS of claim 13, wherein an address of the IMS-AS is registered in a HSS, wherein the IMS-AS supports monitoring of one or more IMS DC events.

Images