DESC:
FORM 2

THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003

COMPLETE SPECIFICATION
(See section 10 and rule 13)
1. TITLE OF THE INVENTION
METHOD AND SYSTEM FOR HANDLING SHORT MESSAGE SERVICE (SMS)

2. APPLICANT(S)
NAME NATIONALITY ADDRESS
JIO PLATFORMS LIMITED INDIAN OFFICE-101, SAFFRON, NR. CENTRE POINT, PANCHWATI 5 RASTA, AMBAWADI, AHMEDABAD 380006, GUJARAT, INDIA
3.PREAMBLE TO THE DESCRIPTION

THE FOLLOWING SPECIFICATION PARTICULARLY DESCRIBES THE NATURE OF THIS INVENTION AND THE MANNER IN WHICH IT IS TO BE PERFORMED.

FIELD OF THE INVENTION
[0001] The present invention relates generally to a telecom network, and in particular, to a method and a system for handling delivery of Short Message Service (SMS) in cases of multiple devices being registered on the same number in a communication network.
BACKGROUND OF THE INVENTION
[0002] Short Message/Messaging Service, commonly abbreviated as SMS, is a text messaging service component in a communications network, Internet and mobile device systems. The SMS uses standardized communication protocols that let mobile devices exchange short text messages.
[0003] In SMS over an IP Multimedia Subsystem (IMS) communication, the SMS is encapsulated in a Session Initiation Protocol (SIP) message and carried over an IMS core network to a short message service center (SMSC). The IP Short Messaging Gateway (IPSMGW) network element provides an interconnection between a Global System for Mobile Communications-Universal Mobile Telecommunications System (GSM-UMTS) network and a Long Term Evolution- Evolved Packet Core (LTE-EPC) network for sending and receiving the SMSs.
[0004] It is possible to use multiple devices for a single number. For example, a mobile phone and a smart watch may be registered on the same number. All the multiple devices may have the same number registered on them so that calls can be answered from any of the devices. But, when the SMS has to be delivered, not all the devices registered on the number may be compatible with SMS services and it may be required to select only one of the devices such as the mobile phone as other devices such as the smart watch may not support SMS functionality. In this case, if a device from the multiple device is chosen at random, the delivery might fail. For example, when the delivery is tried on a device which does not support SMS functionality such as the smart watch.
[0005] It is desired to avoid such SMS delivery failure in the communication network. Therefore, there is a need for a system and a method in the art which is able to handle SMS delivery in case of multiple devices being registered on the same number without reporting a failure and deliver it with a higher success rate to the correct device for best user experience.
SUMMARY OF THE INVENTION
[0006] One or more embodiments of the present disclosure provide a system and a method for handling a SMS in a communications network..
[0007] In one aspect of the present invention, a method of handling a SMS is disclosed. The method includes receiving, by one or more processors, the SMS from a first user equipment (UE) for delivery to one or more user equipment’s (UEs). Further, the method includes sending, by the one or more processors, a User-Data-Request (UDR) command (or UDR) to a Home Subscriber Server (HSS) for retrieving information associated with the one or more UEs. Further, the method includes receiving, by the one or more processors, from the HSS an IP Multimedia Private Identity (IMPI) and International Mobile Equipment Identity (IMEI) associated with each UE of the one or more UEs. Further, the method includes detecting, by the one or more processors, presence of a soft tag with the IMPI of each of the UE of the one or more UEs. Further, the method includes barring transmission, by the one or more processors, of the SMS to each of the UE that has the soft tag associated with the IMPI.
[0008] In an embodiment, the method further includes transmitting, by the one or more processors, the SMS to a user equipment that does not have the soft tag associated with the IMPI.
[0009] In an embodiment, presence of the soft tag indicates the user equipment is not compatible in receiving the SMS.
[0010] In an embodiment, the method further includes storing, by the one or more processors, the SMS in a database for attempting transmission of the SMS again, when the soft tag is undetected. Further, the method includes repeating, by the one or more processors, the step of detecting the presence of the soft tag for another UE of the one or more UEs, after a predefined time interval. Further, the method includes transmitting, by the one or more processors, the stored SMS upon detecting the soft tag, to the other UE not associated with the soft tag.
[0011] In an embodiment, the method further includes checking, by the one or more processor, a user context in a database upon receiving the SMS, wherein the user context includes IMPI and IMEI information of the one or more UEs that are compatible in receiving the SMS. This registration is performed at the IPSMGW by an auxiliary device, which sets the user context at the HSS. During MT, a serving IPSMGW obtains user context from the HSS.
[0012] In an embodiment, when the presence of the soft tag with the IMPI of each of the UE of the one or more UEs is not detected by the one or more processors, then the information pertaining to a Serving Call Session Control Function (SCSCF) address and the IMEI is transmitted in the SMS to a user.
[0013] In another aspect of the present invention, a system for handling a SMS is disclosed. The system includes a transceiver unit and a detecting unit. The transceiver unit is configured to receive the SMS from a from a first UE for delivery to one or more UEs. Further, the transceiver unit is configured to send a UDR command (or UDR) to a HSS for retrieving information associated with the one or more UEs. Further, the transceiver unit is configured to receive, from the HSS, an IMPI and IMEI associated with each UE of the one or more UEs. The detecting unit is configured to detect presence of a soft tag with the IMPI of each of the UE of the one or more UEs. Furthermore, the transceiver unit is configured to bar transmission of the SMS to each of the UE that has the soft tag associated with the IMPI.
[0014] In another aspect of the present invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions that, when executed by a processor, cause the processor to receive the SMS from a first UE for delivery to one or more UEs, send a UDR to a HSS for retrieving information associated with the one or more UEs, receive, from the HSS, an IMPI and IMEI associated with each UE of the one or more UEs, detect presence of a soft tag with the IMPI of each of the UE of the one or more UEs, and bar transmission of the SMS to each of the one or more UEs that has the soft tag associated with the IMPI.
[0015] Other features and aspects of this invention will be apparent from the following description and the accompanying drawings. The features and advantages described in this summary and in the following detailed description are not all-inclusive, and particularly, many additional features and advantages will be apparent to one of ordinary skill in the relevant art, in view of the drawings, specification, and claims hereof. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necessary to determine such inventive subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS
[0016] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0017] FIG. 1 is an exemplary block diagram of an environment for handling a SMS, according to various embodiments of the present disclosure.
[0018] FIG. 2 is a block diagram of a system of FIG. 1, according to various embodiments of the present disclosure.
[0019] FIG. 3 is an example schematic representation of the system of FIG. 1 in which various entities operations are explained, according to various embodiments of the present system.
[0020] FIG. 4 is a block diagram illustrating a logical architecture of an IP Short Message Gateway (IPSMGW), in accordance with an embodiment of the invention.
[0021] FIG. 5 shows a sequence flow diagram illustrating a method for handling the SMS in a communications network, according to various embodiments of the present disclosure.
[0022] FIG. 6 is an example flow diagram illustrating the method for handling SMS service with regard to multiple devices, in accordance with an embodiment of the invention.
[0023] Further, skilled artisans will appreciate that elements in the drawings are illustrated for simplicity and may not have been 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 benefit of the description herein.
[0024] The foregoing shall be more apparent from the following detailed description of the invention.

DETAILED DESCRIPTION OF THE INVENTION
[0025] Some embodiments of the present disclosure, illustrating all its features, will now be discussed in detail. It must also be noted that as used herein and in the appended claims, the singular forms "a", "an" and "the" include plural references unless the context clearly dictates otherwise.
[0026] Various modifications to the embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. However, one of ordinary skill in the art will readily recognize that the present disclosure including the definitions listed here below are not intended to be limited to the embodiments illustrated but is to be accorded the widest scope consistent with the principles and features described herein.
[0027] A person of ordinary skill in the art will readily ascertain that the illustrated steps detailed in the figures and here below are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0028] Various embodiments of the invention provide a method of handling a SMS in a communications network. The method includes receiving, by one or more processors, the SMS from a first UE for delivery to one or more UEs. Further, the method includes sending, by the one or more processors, a UDR to a HSS for retrieving information associated with the one or more UEs. Further, the method includes receiving, by the one or more processors, from the HSS an IMPI and IMEI associated with each UE of the one or more UEs. Further, the method includes detecting, by the one or more processors, presence of a soft tag with the IMPI of each of the UE of the one or more UEs. Further, the method includes barring transmission, by the one or more processors, of the SMS to each of the UE that has the soft tag associated with the IMPI.
[0029] The present invention provides a solution for handling SMS delivery in case of multiple devices being registered on the same number by identifying the non-compatible device out of the multiple devices using an identifier such as ‘soft’ tag and the like.
[0030] For regular user registration, the IP Short Message Gateway (IPSMGW) stores the registration data provided by the SCSCF in its database and notifies a HLR (Home Location Register) that it will handle any future messages for that user. In case of multiple devices, the mobile device follows the aforementioned steps, while a smart watch registers with a soft SIM in the communication network since it lacks a physical SIM card. During registration, the watch includes an indication of 'soft' in its private identity within the registration request.
[0031] In accordance with an embodiment of the invention, when the IPSMGW receives this header, it recognizes the device as the smart watch and disregards it for SMS delivery if the SMS services are not available for the smart watches. This is performed at the IPSMGW which takes all SMS service-related decisions in an IMS network.
[0032] This is possible because the IPSMGW has information of all the devices registered in the communication network and it can efficiently use this information for better service experience. The IPSMGW is an IMS application server which handles SIP based messaging services for IMS subscribers. An IP Multimedia Subsystem or IMS is a standards-based architectural framework for delivering multimedia communications services such as voice, video and text messaging over IP networks. In addition, the IPSMGW will interact with a legacy SMSC using a Mobile Application Part (MAP) signalling in order to allow the IMS to SMS conversion and distribution.
[0033] FIG. 1 illustrates an exemplary block diagram of an environment (100) for for handling a SMS in a communications network (106), according to various embodiments of the present disclosure. The environment (100) comprises a plurality of user equipment’s (UEs) 102-1, 102-2, ……,102-n. The at least one UE (102-n) from the plurality of the UEs (102-1, 102-2, ……102-n) is configured to connect to a system (108) via the communication network (106). Hereafter, label for the plurality of UEs or one or more UEs is 102.
[0034] In accordance with yet another aspect of the exemplary embodiment, the plurality of UEs (102) may be a wireless device or a communication device that may be a part of the system (108). The wireless device or the UE (102) may include, but are not limited to, a handheld wireless communication device (e.g., a mobile phone, a smart phone, a phablet device, and so on), a wearable computer device (e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and/or any other type of computer device with wireless communication or VoIP capabilities. In an embodiment, the UEs may include, but are not limited to, any electrical, electronic, electro-mechanical or an equipment or a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device, wherein the computing device may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as camera, audio aid, a microphone, a keyboard, input devices for receiving input from a user such as touch pad, touch enabled screen, electronic pen and the like. It may be appreciated that the UEs may not be restricted to the mentioned devices and various other devices may be used. A person skilled in the art will appreciate that the plurality of UEs (102) may include a fixed landline, a landline with assigned extension within the communication network (106).
[0035] The plurality of UEs (102) may comprise a memory such as a volatile memory (e.g., RAM), a non-volatile memory (e.g., disk memory, FLASH memory, EPROMs, etc.), an unalterable memory, and/or other types of memory. In one implementation, the memory might be configured or designed to store data. The data may pertain to attributes and access rights specifically defined for the plurality of UEs (102). The UE (102) may be accessed by the user, to receive the requests related to an order determined by the system (108). The communication network (106), may use one or more communication interfaces/protocols such as, for example, Voice Over Internet Protocol (VoIP), 802.11 (Wi-Fi), 802.15 (including Bluetooth™), 802.16 (Wi-Max), 802.22, Cellular standards such as Code Division Multiple Access (CDMA), CDMA2000, Wideband CDMA (WCDMA), Radio Frequency Identification (e.g., RFID), Infrared, laser, Near Field Magnetics, etc.
[0036] The system (108) is communicatively coupled to a server (104) via the communication network (106). The server (104) can be, for example, but not limited to a standalone server, a server blade, a server rack, an application server, a bank of servers, a business telephony application server (BTAS), a server farm, a cloud server, an edge server, home server, a virtualized server, one or more processors executing code to function as a server, or the like. In an implementation, the server (104) may operate at various entities or a single entity (include, but is not limited to, a vendor side, a service provider side, a network operator side, a company side, an organization side, a university side, a lab facility side, a business enterprise side, a defence facility side, or any other facility) that provides service.
[0037] The communication network (106) includes, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof. The communication network (106) may include, but is not limited to, a Third Generation (3G), a Fourth Generation (4G), a Fifth Generation (5G), a Sixth Generation (6G), a New Radio (NR), a Narrow Band Internet of Things (NB-IoT), an Open Radio Access Network (O-RAN), and the like.
[0038] The communication network (106) may also include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The communication network (106) may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, a VOIP or some combination thereof.
[0039] One or more network elements can be, for example, but not limited to a base station that is located in the fixed or stationary part of the communication network (106). The base station may correspond to a remote radio head, a transmission point, an access point or access node, a macro cell, a small cell, a micro cell, a femto cell, a metro cell. The base station enables transmission of radio signals to the UE or mobile transceiver. Such a radio signal may comply with radio signals as, for example, standardized by a 3GPP or, generally, in line with one or more of the above listed systems. Thus, a base station may correspond to a NodeB, an eNodeB, a Base Transceiver Station (BTS), an access point, a remote radio head, a transmission point, which may be further divided into a remote unit and a central unit.
[0040] 3GPP: The term “3GPP” is a 3rd Generation Partnership Project and is a collaborative project between a group of telecommunications associations with the initial goal of developing globally applicable specifications for Third Generation (3G) mobile systems. The 3GPP specifications cover cellular telecommunications technologies, including radio access, core network, and service capabilities, which provide a complete system description for mobile telecommunications. The 3GPP specifications also provide hooks for non-radio access to the core network, and for networking with non-3GPP networks.
[0041] The system (108) may include one or more processors (202) coupled with a memory (204), wherein the memory (204) may store instructions which when executed by the one or more processors (202) may cause the system (108) executing requests in the communication network (106) or the server (104). An exemplary representation of the system (108) for such purpose, in accordance with embodiments of the present disclosure, is shown in FIG. 2 as system (108). In an embodiment, the system (108) may include one or more processor(s) (202). The one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, edge or fog microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in the memory (204) of the system (108). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service.
[0042] The environment (100) further includes the system (108) communicably coupled to the remote server (104) and each UE of the plurality of UEs (102) via the communication network (106). The remote server (104) is configured to execute the requests in the communication network (106).
[0043] The system (108) is adapted to be embedded within the remote server (104) or is embedded as the individual entity. The system (108) is designed to provide a centralized and unified view of data and facilitate efficient business operations. The system (108) is authorized to access to update/create/delete one or more parameters of their relationship between the requests for the workflow, which gets reflected in real-time independent of the complexity of network.
[0044] In another embodiment, the system (108) may include an enterprise provisioning server (for example), which may connect with the remote server (104). The enterprise provisioning server provides flexibility for enterprises, ecommerce, finance to update/create/delete information related to the requests in real time as per their business needs. A user with administrator rights can access and retrieve the requests for the workflow and perform real-time analysis in the system (108).
[0045] The system (108) may include, by way of example but not limitation, one or more of a standalone server, a server blade, a server rack, a bank of servers, a business telephony application server (BTAS), a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof. In an implementation, system (108) may operate at various entities or single entity (for example include, but is not limited to, a vendor side, service provider side, a network operator side, a company side, an organization side, a university side, a lab facility side, a business enterprise side, ecommerce side, finance side, a defence facility side, or any other facility) that provides service.
[0046] However, for the purpose of description, the system (108) is described as an integral part of the remote server (104), without deviating from the scope of the present disclosure. Operational and construction features of the system (108) will be explained in detail with respect to the following figures.
[0047] FIG. 2 illustrates a block diagram of the system (108) provided for handling the SMS, according to one or more embodiments of the present invention. As per the illustrated embodiment, the system (108) includes the one or more processors (202), the memory (204), an input/output interface unit (206), a display (208), an input device (210), and a centralized database (or database) (214). Further the system (108) may comprise one or more processors (202). The one or more processors (202), hereinafter referred to as the processor (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, single board computers, and/or any devices that manipulate signals based on operational instructions. As per the illustrated embodiment, the system (108) includes one processor. However, it is to be noted that the system (108) may include multiple processors as per the requirement and without deviating from the scope of the present disclosure.
[0048] The information related to the request may be provided or stored in the memory (204) of the system (108). Among other capabilities, the processor (202) is configured to fetch and execute computer-readable instructions stored in the memory (204). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may include any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as disk memory, EPROMs, FLASH memory, unalterable memory, and the like.
[0049] The memory (204) may comprise any non-transitory storage device including, for example, volatile memory such as Random-Access Memory (RAM), or non-volatile memory such as Electrically Erasable Programmable Read-only Memory (EPROM), flash memory, and the like. In an embodiment, the system (108) may include an interface(s). The interface(s) may comprise a variety of interfaces, for example, interfaces for data input and output devices, referred to as input/output (I/O) devices, storage devices, and the like. The interface(s) may facilitate communication for the system. The interface(s) may also provide a communication pathway for one or more components of the system. Examples of such components include, but are not limited to, processing unit/engine(s) and a database. The processing unit/engine(s) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s).
[0050] The information related to the requests may further be configured to render on the user interface (206). The user interface (206) may include functionality similar to at least a portion of functionality implemented by one or more computer system interfaces such as those described herein and/or generally known to one having ordinary skill in the art. The user interface (206) may be rendered on the display (208), implemented using Liquid Crystal Display (LCD) display technology, Organic Light-Emitting Diode (OLED) display technology, and/or other types of conventional display technology. The display (208) may be integrated within the system (108) or connected externally. Further the input device(s) (210) may include, but not limited to, keyboard, buttons, scroll wheels, cursors, touchscreen sensors, audio command interfaces, magnetic strip reader, optical scanner, etc.
[0051] The centralized database (214) may be communicably connected to the processor (202) and the memory (204). The centralized database (214) may be configured to store and retrieve the request pertaining to features, or services or workflow of the system (108), access rights, attributes, approved list, and authentication data provided by an administrator. Further the remote server (104) may allow the system (108) to update/create/delete one or more parameters of their information related to the request, which provides flexibility to roll out multiple variants of the request as per business needs. In another embodiment, the centralized database (214) may be outside the system (108) and communicated through a wired medium and wireless medium.
[0052] Further, the processor (202), in an embodiment, may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor (202). In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processor (202) may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor (202) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory (204) may store instructions that, when executed by the processing resource, implement the processor (202). In such examples, the system (108) may comprise the memory (204) storing the instructions and the processing resource to execute the instructions, or the memory (204) may be separate but accessible to the system (108) and the processing resource. In other examples, the processor (202) may be implemented by an electronic circuitry.
[0053] In order for the system (108) to handle the SMS, the processor (202) includes a transceiver unit (216) and a detecting unit (218). The transceiver unit (216) and the detecting unit (218) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor (202). In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processor (202) may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor (202) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory (204) may store instructions that, when executed by the processing resource, implement the processor. In such examples, the system (108) may comprise the memory (204) storing the instructions and the processing resource to execute the instructions, or the memory (204) may be separate but accessible to the system (108) and the processing resource. In other examples, the processor (202) may be implemented by the electronic circuitry.
[0054] In order for the system (108) to handle the SMS, the transceiver unit (216) and the detecting unit (218) are communicably coupled to each other. In an example embodiment, the transceiver unit (216) receives the SMS from the first UE for delivery to the one or more UEs (102). Further, the transceiver unit (216) sends the UDR command to the HSS (424) for retrieving information associated with the one or more UEs (102). Further, the transceiver unit (216) receives, from the HSS (424), the IMPI and the IMEI associated with each UE of the one or more UEs (102). The detecting unit (218) detects presence of a soft tag with the IMPI of each of the UE of the one or more UEs (102). The transceiver unit (216) bars transmission of the SMS to each of the UE that has the soft tag associated with the IMPI. In an embodiment, presence of the soft tag indicates the each of the UE of the one or more UEs (102) is not compatible in receiving the SMS.
[0055] In an embodiment, the transceiver unit (216) transmits the SMS to another UE of the one or more UEs (102) that does not have the soft flag associated with the IMPI. In an embodiment, the database (214) stores the SMS for attempting transmission of the SMS again, when the soft tag is undetected.
[0056] In an embodiment, the detecting unit (218) repeats the step of detecting the presence of the soft tag for another user equipment, after the predefined time interval. The predefined time interval is set by the user, the system (108), or a service provider. The transceiver unit (216) transmits the stored SMS upon detecting the soft tag, to the other UE not associated with the soft tag.
[0057] In an embodiment, the detecting unit (218) checks the user context in the database upon receiving the SMS, wherein the user context includes the IMPI and the IMEI information of the one or more UEs (102) that are compatible in receiving the SMS. This registration is performed at the IPSMGW (402) by an auxiliary device, which sets the user context at the HSS. During mobile termination (MT), a serving IPSMGW (402) (as shown in FIG. 4) obtains user context from the HSS (424)
[0058] In an embodiment, when the presence of the soft tag with the IMPI of each of the UE of the one or more UEs (102) is not detected by the detecting unit (218), then the information pertaining to a SCSCF address and the IMEI is transmitted in the SMS to a user.
[0059] FIG. 3 is an example schematic representation of the system (300) of FIG. 1 in which various entities operations are explained, according to various embodiments of the present system. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the first UE (102-1) and the system (108) for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.
[0060] As mentioned earlier, the first UE (102-1) includes one or more primary processors (305) communicably coupled to the one or more processors (202) of the system (108). The one or more primary processors (305) are coupled with a memory (310) storing instructions which are executed by the one or more primary processors (305). Execution of the stored instructions by the one or more primary processors (305) enables the UE (102-1). The execution of the stored instructions by the one or more primary processors (305) further enables the UE (102-1) to execute the requests in the communication network (106).
[0061] As mentioned earlier, the one or more processors (202) is configured to transmit a response content related to the request to the UE (102-1). More specifically, the one or more processors (202) of the system (108) is configured to transmit the response content from a kernel (315) to at least one of the UE (102-1). The kernel (315) is a core component serving as the primary interface between hardware components of the UE (102-1) and the system (108). The kernel (315) is configured to provide the plurality of response contents hosted on the system (108) to access resources available in the communication network (106). The resources include one of a Central Processing Unit (CPU), memory components such as Random Access Memory (RAM) and Read Only Memory (ROM).
[0062] As per the illustrated embodiment, the system (108) includes the one or more processors (202), the memory (204), the input/output interface unit (206), the display (208), and the input device (210). The operations and functions of the one or more processors (202), the memory (204), the input/output interface unit (206), the display (208), and the input device (210) are already explained in FIG. 2. For the sake of brevity, we are not explaining the same operations (or repeated information) in the patent disclosure. Further, the processor (202) includes the transceiver unit (216) and the detecting unit (218). The operations and functions of the transceiver unit (216) and the detecting unit (218) are already explained in FIG. 2. For the sake of brevity, we are not explaining the same operations (or repeated information) in the patent disclosure.
[0063] FIG. 4 is a block diagram illustrating a logical architecture (400) of the IPSMGW (402), in accordance with an embodiment of the invention. Referring to FIG. 4, the following table describes the interaction, interface and purpose of various elements, in accordance with an embodiment of the invention.
IPSMGW System NE Integration with Interface Purpose
IPSMGW Application SCSCF (408) ISC over SIP The ISC interface connects S-CSCF and Application Server(s). S-CSCF will trigger IPSMGW (402) for 3rd Party Registrations and for forwarding SMS originated from UE towards the IPSMGW(402).
MNP DB SIP The IPSMGW (402) will perform MNP query by using SIP MESSAGE method to find RN (Routable Number) and outbound Mobile Numbers. The Mobile number portability (MNP) server (418) shall respond back with 302- Redirect, CONTACT header of the response shall contain the LRN and domain info as required. This integration is done via F5 load balancer (416).
OCS RO over diameter The IPSMGW (402) connects to Online Charging System, to provide diameter based IMS online charging.
This interface is via the Diameter Routing Agent (DRA).
Charging for pre-paid and post-paid subscribers will be via an Online charging system (OCS) (422).
HSS Sh The IPSMGW (402) will communicate with the HSS (424) over Sh interface to fetch user registration data.
CP SMPP The IPSMGW (402) integrates with CP (content provider) over SMPP interface for P2A or A2P SMS service. This integration is done via a F5 load balancer (412) that is coupled with the SMPP CP (414).
A2P IPSMGW SMPP The IPSMGW (402) deployed for A2P traffic connects with P2P IPSMGW over SMPP interface to transfer SMPP request from UE to A2P IPSMGW (402). This integration is done via a F5 load balancer.
Service Capabilities Exposure Function (SCEF) (426) T4 over Diameter The IPSMGW (402) connects with the SCEF (426) over T4 interface to receive device trigger messages
HSS S6c over diameter The IPSMGW (402) connects with the HSS (424) over S6c interface to fetch terminating IPSMGW address of user.
Mobility Management Entity (MME) (428) Sgd over diameter The IPSMGW (402) connects with the MME (428) over SGd interface to terminate the device trigger message to user.
IPSMGW Signalling Frontend (FE) HLR MAP-E IPSMGW FE connects with HLR over MAP-E interface to fetch registration status of end user. This integration is done via a Signal Transfer Point (STP) (406).
EMS (404) REST IPSMGW FE will integrate with Element Management System (EMS) (404) over REST interface to share FCAPS data of IPSMGW application, IPSMGW signalling front end and IPSMGW antispam manager. It will primarily support fault management, performance management and configuration management of these nodes.
EMS OSS/BSS The EMS (404) integrates with north bound OSS/BSS nodes i.e. TeMIP, MyCOM, HPOO, Granite, DnR for sharing FCAPs data with operations team.
[0064] Unified Data Management: The UDM, as part of UE authentication procedures for 3GPP access generates AKA authentication credentials and provides them to an AUSF (Authentication Service Function) for subscriber authentication. Similarly, for non-3GPP access, EAP-AKA’ is supported. Subscriber identities e.g. public identity (SUPI) and private identity (SUCI), stored in the UDM, are used to perform user identification procedures. Based on the subscription data stored in the UDM, a service access is granted to the UE. A Subscriber Data Management (SDM) supports various UDM operations such as Subscriber Identification Management based on private and public identity, private identity concealment, authentication vector generation, authorized access to network based on subscription data, Service and Session continuity, Subscriber Registration/Attach management, Subscription Management, SMS Management, Lawful Interception, especially in case subscriber is out-roaming as UDM is the only point of source for roaming PLMN, External Parameter Provisioning to control UE behavior. It also supports MT-SMS delivery functionality and other SMS management procedures. Each specialized functionality of UDM runs as a separate Micro Service (MS). All above operations are exposed towards other NFs communicating over following “Nudm” microservices;
a) SubscriberDataManagement,
b) UEContextManagement,
c) UEAuthentication,
d) EventExposure, and
e) ParameterProvision.
[0065] The HSS (424) is a carrier grade, high capacity, fault tolerant and scalable cluster solution designed to serve millions of devices in the communication network (106). It is a converged solution developed in-house to serve 2G/3G/4G and 5G subscribers. It has a master database of the mobile subscribers storing subscription related information. The HSS (424) supports a Home Location Register (HLR) and Equipment Identification Register (EIR) functionality compliant to 3GPP specifications.
[0066] The HSS (424) supports S6a, S13, S6t, S6c, Cx, Sh, Zh and SlHdiameter interfaces and is capable to integrate with any 3GPP compliant MME (428), the SCEF (426), the SMSC, the CSCF, an AS and a Gateway Mobile Location Centre (GMLC). The HSS (424) also supports 3GPP MAP interfaces C, D, J and Gr and integrate with a GMSC, a VLR, a gsmSCF and a GGSN to provide services to internationally roaming subscribers latching to legacy 2G/3G networks.
[0067] The HSS diameter FE hosts diameter application interfaces e.g. S6a, S13, S6t, S6c and executes procedures and business logic. A diameter front end is stateless and does not need to maintain sessions.
[0068] Application FEs integrates with a Diameter Relay agent (DRA) (420) for sending and receiving of diameter messages. It has the capability to connect to multiple DRAs for supporting DRA redundancy. It also supports diameter application-based load distribution and if required may connect to different DRAs for different set of Diameter application IDs. It supports Active/Active, N-Way Active and Active/Standby connections with the DRA (420). In case of Active/Active or N-way Active connections, it distributes all HSS initiated transactions on the DRAs.
[0069] Provisioning Gateway (P-GW): Provisioning server hosts application logic for create/modify/display/delete of subscription information, authentication information, equipment information etc. It supports NETCONF/SSH and Restful/HTTP interfaces. It Supports both client and server-side validation of input parameters for syntax and semantic checks. It provides lightweight CLI for all provisioning requirements. Provisioning server supports creation of multiple templates referred to as Class of Service to ease provisioning of subscribers. It integrates with OSS nodes over secured Command Line Interface (CLI) there is no restriction on number of active users/sessions.
[0070] Based on the user requirements a suitable role can be assigned to a user. It has provision for creation of multiple roles/privileges to run commands. One role can be assigned to multiple users. The provisioning application connects with application front end nodes to meet the requirements of diameter message invocation in case of admin update of subscription information. It connects with a cluster manager for fault, configuration, accounting, performance, security (FCAPs) and node management.
[0071] If the HSS (424) is deployed as a standalone node, then P-GW will be deployed as part of HSS cluster. Else if this component is deployed as a whole SDM solution then P-GW will be deployed as a part of the UDM Cluster.
[0072] FIG. 5 is a flow chart (500) illustrating a method for for handling the SMS, according to various embodiments of the present system.
[0073] At step 502, the method includes receiving the SMS from the first UE for delivery to the one or more UEs (102). In an embodiment, the method allows the transceiver unit (216) to receive the SMS from the first UE for delivery to the one or more UEs (102).
[0074] At step 504, the method includes sending the UDR to the HSS (424) for retrieving information associated with the one or more UEs (102). In an embodiment, the method allows the transceiver unit (216) to send the UDR to the HSS (424) for retrieving information associated with the one or more UEs (102).
[0075] At step 506, the method includes receiving, from the HSS (424), the IMPI and the IMEI associated with each UE of the one or more UEs (102). In an embodiment, the method allows the transceiver unit (216) to receive, from the HSS (424), the IMPI and the IMEI associated with each UE of the one or more UEs (102).
[0076] At step 508, the method includes detecting presence of the soft tag with the IMPI of each of the UE of the one or more UEs (102). In an embodiment, the method allows the detecting unit (218) to detect presence of the soft tag with the IMPI of each of the UE of the one or more UEs (102).
[0077] At step 510, the method includes barring transmission of the SMS to each of the UE that has the soft tag associated with the IMPI. In an embodiment, the method allows the transceiver unit (216) to bar transmission of the SMS to each of the UE that has the soft tag associated with the IMPI.
[0078] At step 512, the method includes storing the SMS in the database for attempting transmission of the SMS again, when the soft tag is undetected. In an embodiment, the method allows the database to store the SMS for attempting transmission of the SMS again, when the soft tag is undetected.
[0079] At step 514, the method includes repeating the step of detecting the presence of the soft tag for another UE of the one or more UEs (102), after the predefined time interval. In an embodiment, the method allows the detecting unit (218) to repeat the step of detecting the presence of the soft tag for another UE of the one or more UEs (102), after the predefined time interval.
[0080] At step 516, the method includes transmitting the stored SMS upon detecting the soft tag, to the other UE not associated with the soft tag. In an embodiment, the method allows the transceiver unit (216) to transmit the stored SMS upon detecting the soft tag, to the other UE not associated with the soft tag
[0081] FIG. 6 is an example flow diagram (600) illustrating the method for handling SMS service with regard to multiple devices, in accordance with an embodiment of the invention. Referring to FIG. 6, at the time of registration, the IPSMGW (402) checks the TPR (Third Party Registration) request received and verifies the IMPI data in a REGISTER request body. The IPSMGW (402) checks if the “soft” tag is present in the IMPI data. The IP Multimedia Subsystem (IMS) Private Identity is a unique permanently allocated global identity assigned by the home network operator, it has the form of a Network Access Identifier (NAI) and is used, for example, for Registration, Authorization, Administration, and Accounting purposes.
[0082] If the “soft” tag is present in the IMPI data, the IPSMGW (402) replies with, for example, 200OK. The reply 200OK is a success response and is sent so that the request is not marked as failed but at its end the IPSMGW (402) will drop it and will not save anything related to the request. The IPSMGW (402) ignores the request so that SMS service is restricted to that device. It may be apparent that 200OK and any other such command is based upon standards in use and may vary as per the standards.
[0083] Referring to FIG. 6, in case of terminating message, the IPSMGW (402) has to identify where to deliver SMS whether on the mobile device or the watch. When any SMS is received at terminating IPSMGW (402), the IPSMGW (402) checks the user context present in the database.
[0084] In case where no user context is present, the IPSMGW (402) sends a UDR request to the HSS (424) with data reference as Repository Data and with service indication as TPR.
[0085] The HSS (424) responds to the request with User Data Answer (UDA) and includes sh-user-data. This data includes IMPIs and IMEIs associated with all the devices registered for the user. Once this data is received, the IPSMGW (402) checks for the ‘soft’ tag associated with the IMPI of registered device.
[0086] If soft tag is present in IMPI, the IPSMGW (402) ignores this data. For example, 405874999997598@soft.ims.mnc874.mcc405.3gppnetwork.org.
[0087] Alternatively, if the ‘soft’ tag is not present, i.e., a mobile device registration data is present and IMPI-state is 1 i.e., registered, then the IPSMGW (402) fetches its SCSCF address and IMEI. This information is sent in the message towards terminating user. Using IMEI and SCSCF address in the profile, the SMS is processed successfully.
[0088] In an embodiment, if IMPI-state is 0 i.e., NOT registered, the above step will not be performed and the message may be stored in the data base for retry at predetermined intervals of time.
[0089] In an embodiment, the IPSMGW (402) may have the user context for only the mobile device and not for the watch, wherein the SMS even in case of multiple devices will be terminated towards mobile device only.
[0090] Referring to FIG. 6, at step 602, the method includes checking the registration context in the centralized database (214). At step 604, the method includes detecting that the registration context is present in the centralized database (214). At step 606, the method includes sending the UDR request to the HSS (424) to get the user data. At step 608, the method includes checking the IMPI data in the UDA for both the soft tag and without the soft tag.
[0091] At step 610, the method includes determining whether the soft tag is present? If the soft tag is present then, at step 612, the method includes determining whether the IMPI state is 1 for the IMPI without soft tag. If the IMPI state is not 1 for the IMPI without the soft tag then, at step 614, the method includes storing the message in the database (214) for retry. If the IMPI state is 1 for the IMPI without the soft tag then, at step 618, the method includes using the IMEI and the SCSCF address in the profile and processing the SMS successfully.
[0092] If the soft tag is not present then, at step 616, the method includes determining whether the IMPI state is 1. If the IMPI state is 1 then, at step 618, the method includes using the IMEI and the SCSCF address in the profile and processing the SMS successfully. If the IMPI state is not 1 then, at step 620, the method includes storing the message in the database (214) for retry.
[0093] Advantageously, the invention provides for handling SMS delivery with a higher success rate in case of an incompatible device without affecting the system KPI. It improves experience and enables higher success rate for SMS delivery. This solution reduces the chances of failure due to device incompetency as SMS will be delivered only to mobile device instead of watch.
[0094] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIGS. 1-6) are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0095] Method steps: A person of ordinary skill in the art will readily ascertain that the illustrated steps are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0096] The present invention offers multiple advantages over the prior art and the above listed are a few examples to emphasize on some of the advantageous features. The listed advantages are to be read in a non-limiting manner.

REFERENCE NUMERALS
[0097] Environment - 100
[0098] UEs– 102, 102-1-102-n
[0099] Server - 104
[00100] Communication network – 106
[00101] System – 108
[00102] Processor – 202
[00103] Memory – 204
[00104] User Interface – 206
[00105] Display – 208
[00106] Input device – 210
[00107] Centralized Database – 214
[00108] Transceiver unit – 216
[00109] Detecting unit - 218
[00110] System - 300
[00111] Primary processors -305
[00112] Memory– 310
[00113] Kernel– 315
[00114] Logical architecture - 400
[00115] IPSMGW – 402
[00116] EMS – 404
[00117] STP – 406
[00118] SCSCF – 408
[00119] F5 Load balancer – 412, 416
[00120] SMPP CP – 414
[00121] MNP server – 418
[00122] DRA – 420
[00123] OCS – 422
[00124] HSS - 424
[00125] SCEF - 426
[00126] MME - 428

,CLAIMS:CLAIMS:
We Claim
1. A method of handling Short Message Service (SMS), the method comprising the steps of:
receiving, by one or more processors (202), the SMS from a first user equipment (UE) for delivery to one or more user equipment’s (UEs) (102);
sending, by the one or more processors (202), a User-Data-Request (UDR) to a Home Subscriber Server (HSS) (424) for retrieving information associated with the one or more UEs (102);
receiving, by the one or more processors (202), from the HSS (424) an IP Multimedia Private Identity (IMPI) and an International Mobile Equipment Identity (IMEI) associated with each UE of the one or more UEs (102);
detecting, by the one or more processors (202), presence of a soft tag with the IMPI of each of the UE of the one or more UEs (102); and
barring transmission, by the one or more processors (202), of the SMS to each of the UE that has the soft tag associated with the IMPI.

2. The method as claimed in claim 1, wherein the method further comprises:
transmitting, by the one or more processors (202), the SMS to a user equipment that does not have the soft tag associated with the IMPI.

3. The method as claimed in claim 1, wherein presence of the soft tag indicates the user equipment is not compatible in receiving the SMS.

4. The method as claimed in claim 1, wherein the method further comprises:
storing, by the one or more processors (202), the SMS in a database (214) for attempting transmission of the SMS again, when the soft tag is undetected;
repeating, by the one or more processors (202), the step of detecting the presence of the soft tag for another UE of the one or more UEs (102), after a predefined time interval; and
transmitting, by the one or more processors (202), the stored SMS upon detecting the soft tag, to the other UE not associated with the soft tag.

5. The method as claimed in claim 4, wherein the method further comprises:
checking, by the one or more processor (202), a user context in a database (214) upon receiving the SMS, wherein the user context includes an IMPI and an IMEI information of the one or more UEs (102) that are compatible in receiving the SMS.

6. The method as claimed in claim 1, wherein when the presence of the soft tag with the IMPI of each of the UE of the one or more UEs (102) is not detected by the one or more processors (202), then the information pertaining to a Serving Call Session Control Function (SCSCF) address and the IMEI is transmitted in the SMS to a user.

7. A system (108) for handling Short Message Service (SMS), the system (108) comprises:
a transceiver unit (216) configured to:
receive the SMS from a from a first user equipment (UE) for delivery to one or more User Equipment’s (UEs) (102);
send a User-Data-Request (UDR) to a Home Subscriber Server (HSS) (424) for retrieving information associated with the one or more UEs (102); and
receive from the HSS (424) an IP Multimedia Private Identity (IMPI) and an International Mobile Equipment Identity (IMEI) associated with each UE of the one or more UEs (102); and
a detecting unit (218) configured to detect presence of a soft tag with the IMPI of each of the UE of the one or more UEs (102), and
wherein the transceiver unit (216) is configured to bar transmission of the SMS to each of the UE that has the soft tag associated with the IMPI.

8. The system (108) as claimed in claim 7, wherein the transceiver unit (216) is further configured to transmit the SMS to a UE of the one or more UEs (102) that does not have the soft flag associated with the IMPI.

9. The system (108) as claimed in claim 7, wherein presence of the soft tag indicates the each of the UE of the one or more UEs (102) is not compatible in receiving the SMS.

10. The system (108) as claimed in claim 7, wherein the system (108) further comprises:
a database (214) configured to store the SMS for attempting transmission of the SMS again, when the soft tag is undetected.

11. The system (108) as claimed in claim 7, wherein the detecting unit (218) is further configured to repeat the step of detecting the presence of the soft tag for another user equipment, after a predefined time interval, and wherein the transceiver unit (216) is further configured to transmit the stored SMS upon detecting the soft tag, to the other UE not associated with the soft tag.

12. The system (108) as claimed in claim 11, wherein the detecting unit (218) is further configured to check a user context in a database (214) upon receiving the SMS, wherein the user context includes IMPI and IMEI information of the one or more UEs (102) that are compatible in receiving the SMS.

13. The system (108) as claimed in of claim 7, wherein when the presence of the soft tag with the IMPI of each of the UE of the one or more UEs (102) is not detected by the detecting unit (218), then the information pertaining to a Serving Call Session Control Function (SCSCF) address and the IMEI is transmitted in the SMS to a user.

14. A User Equipment (UE) (102-1), comprising:
one or more primary processors (305) communicatively coupled to one or more processors (202) of a system (108), the one or more primary processors (305) coupled with a memory (310), wherein said memory (310) stores instructions which when executed by the one or more primary processors (305) causes the UE (102-1) to:
transmit, a SMS to the one or more processers (202);
wherein the one or more processors (202) is configured to perform the steps as claimed in claim 1.