DESC:FORM 2
THE PATENTS ACT, 1970 (39 OF 1970)
&
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)

SYSTEM AND METHOD FOR TRANSMITTING A MESSAGE IN A WIRELESS COMMUNICATION NETWORK

Jio Platforms Limited, an Indian company, having registered address at Office -101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India

The following complete specification particularly describes the disclosure and the manner in which it is performed.

TECHNICAL FIELD
[0001] The embodiments of the present disclosure generally relate to the field of wireless communication networks. More particularly, the present disclosure relates to a system and a method for transmitting a message in a wireless communication network.
BACKGROUND OF THE INVENTION
[0002] The subject matter disclosed in the background section should not be assumed or construed to be prior art merely due to its mention in the background section. Similarly, any problem statement mentioned in the background section or its association with the subject matter of the background section should not be assumed or construed to have been previously recognized in the prior art.
[0003] With the recent advancements in telecommunication systems, there is a massive increase in the number of users latched to a network. A large number of messages in the form of text, voice, video, and other formats have been exchanged between the users latched to the network. Short message service (SMS) is a standard communication service used in telecommunication systems for forwarding short text messages from a sender device to a recipient device. Using standardized communication protocols, the SMS allows the exchange of the short text messages between mobile phone subscribers belongs to a same service provider or different service providers.
[0004] In a conventional method of transmitting a message to the recipient device, the message is first sent by the sender device to a Short Message Service Center (SMSC). After receiving the message, the SMSC stores the message in a memory until the recipient device alerts the SMSC that the recipient device is registered with the network. Upon receiving the alert, the SMSC forwards the message to the recipient device and removes the message from the memory of the SMSC. If the recipient device is not reachable, for example, turned off or out of range, the SMSC queues the message for later delivery retry.
[0005] Further, the conventional method uses one or more access domains such as, circuit switching and packet switching to provide mobile data services to a subscriber. In circuit-based approaches, the data is carried by a dedicated connection between the sender device and recipient device using a physical switching path. In packet-based approaches, data flow is in the form of packets, where the data is divided into separate segments of information. The subscription of the recipient device is authenticated and registered in a Home Subscriber Server (HSS) or a Home Location Register (HLR).
[0006] However, in the conventional method, network operators deal with multiple technologies in their networks ranging from 2G, 3G, 4G, 5G or fixed networks. Each technology operates on separate access domains. Hence, there is a need for a unified way to manage subscribers across the multiple technologies, while also delivering a high-quality service to the subscribers and ensuring quick and smooth transition of technologies.
[0007] In light of the aforementioned challenges and considerations, there is a need for an improved system and method for supporting message delivery between two user equipment in the wireless communication network irrespective of access domain and network interfaces to improve performance of the network.
SUMMARY
[0008] The following embodiments present a simplified summary in order to provide a basic understanding of some aspects of the disclosed invention. This summary is not an extensive overview, and it is not intended to identify key/critical elements or to delineate the scope thereof. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.
[0009] In an embodiment, a method for transmitting a message in a wireless communication network is disclosed. The method includes receiving, by a reception module of a server from a Message Serving Center (MSC) node associated with a first User Equipment (UE), a subscription request for an alert message. The method further includes subscribing, by a subscription module of the server based on the reception of the subscription request, the MSC node associated with the first UE for the alert message. Further, the method includes storing, by a storage module of the server, a Message Waiting Data (MWD) in a database of the server. Furthermore, the method includes receiving, by the reception module from a MSC node associated with a second UE, a subscriber attach request from the second UE. Further, the method includes determining, by a determining module of the server based on the subscriber attach request from the second UE, whether the second UE is available. Thereafter, the method includes transmitting, by a transmission module of the server based on the MWD, the alert message to the MSC node associated with the first UE to initiate delivery of the message from the first UE to the second UE.
[0010] In some aspects of the present disclosure, the MSC node associated with the first UE subscribes to the alert message upon determining that the second UE is unavailable to receive the message from the first UE.
[0011] In some aspects of the present disclosure, the MSC node associated with the first UE transmits the message to the second UE based on a reception of the alert message.
[0012] In some aspects of the present disclosure, the method further includes determining, by the determination module, whether the second UE is subscribed to the server. The second UE is attached to at least one access domain.
[0013] In some aspects of the present disclosure, the method further includes determining, by the determination module upon determining that the second UE is attached to the at least one access domain, whether the MSC node associated with of the first UE is subscribed to receive the alert message based on the MWD.
[0014] In some aspects of the present disclosure, the at least one access domain is at least one of Circuit Switched (CS), Packet Switched (PS), Evolved Packet System (EPS), and Internet Protocol Multimedia Subsystem (IMS).
[0015] In some aspects of the present disclosure, each of the MSC node associated with the first UE and the MSC node associated with the second UE is at least one of Message Service Centre (MSC), Internet Protocol Short Message Gateway (IP-SM-GW), Short Message Service Center (SMSC), SMS-Internetworking Mobile Switching Center (SMS-IWMSC), and SMS-Gateway Mobile Switching Center (SMS-GMSC).
[0016] In some aspects of the present disclosure, the MWD comprises an address of the MSC node associated with the first UE and a failure reason indicating that the second UE is unavailable.
[0017] In some aspects of the present disclosure, the server supports a Mobile Application Part (MAP) protocol and a diameter protocol for signaling in the at least one access domain.
[0018] In some aspects of the present disclosure, the server stores the MWD received via an interface using the MAP protocol separately from the MWD received via an interface using the diameter protocol.
[0019] In another embodiment, disclosed is a system for transmitting a message in a wireless communication network. The system includes a reception module configured to receive, from a Message Serving Center (MSC) node associated with a first User Equipment (UE), a subscription request for an alert message. The system further includes a subscription module configured to subscribe, based on the reception of the subscription request, the MSC node associated with the first UE for the alert message. Further, the system includes a storage module configured to store a Message Waiting Data (MWD) in a database of a server. The reception module is further configured to receive from a MSC node associated with a second UE, a subscriber attach request from the second UE. Furthermore, the system includes a determining module configured to determine, based on the subscriber attach request from the second UE, whether the second UE is available. Thereafter, the system includes a transmission module configured to transmit, based on the MWD, the alert message to the MSC node associated with the first UE to initiate delivery of the message from the first UE to the second UE.
BRIEF DESCRIPTION OF DRAWINGS
[0020] Various embodiments disclosed herein will become better understood from the following detailed description when read with the accompanying drawings. The accompanying drawings constitute a part of the present disclosure and illustrate certain non-limiting embodiments of inventive concepts disclosed herein. Further, components and elements shown in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. For the purpose of consistency and ease of understanding, similar components and elements are annotated by reference numerals in the exemplary drawings.
[0021] FIG. 1 illustrates a diagram depicting an environment of a wireless communication network, in accordance with an embodiment of the present disclosure.
[0022] FIG. 2 illustrates a block diagram of a system for supporting message delivery in the wireless communication network, in accordance with an embodiment of the present disclosure.
[0023] FIG. 3 illustrates a process flow diagram depicting a method for supporting message delivery between two user equipment in the wireless communication network, in accordance with an embodiment of the present disclosure.
[0024] FIG. 4 illustrates a process flow diagram depicting a method for transmitting a message in the wireless communication network, in accordance with an embodiment of the present disclosure.
DETAILED DESCRIPTION OF THE INVENTION
[0025] Inventive concepts of the present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of one or more embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Further, the one or more embodiments disclosed herein are provided to describe the inventive concept thoroughly and completely, and to fully convey the scope of each of the present inventive concepts to those skilled in the art. Furthermore, it should be noted that the embodiments disclosed herein are not mutually exclusive concepts. Accordingly, one or more components from one embodiment may be tacitly assumed to be present or used in any other embodiment.
[0026] The following description presents various embodiments of the present disclosure. The embodiments disclosed herein are presented as teaching examples and are not to be construed as limiting the scope of the present disclosure. The present disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary design and implementation illustrated and described herein, but may be modified, omitted, or expanded upon without departing from the scope of the present disclosure.
[0027] The following description contains specific information pertaining to embodiments in the present disclosure. The detailed description uses the phrases “in some embodiments” which may each refer to one or more or all of the same or different embodiments. The term “some” as used herein is defined as “one, or more than one, or all.” Accordingly, the terms “one,” “more than one,” “more than one, but not all” or “all” would all fall under the definition of “some.” In view of the same, the terms, for example, “in an embodiment” refers to one embodiment and the term, for example, “in one or more embodiments” refers to “at least one embodiment, or more than one embodiment, or all embodiments.”
[0028] The term “comprising,” when utilized, means “including, but not necessarily limited to;” it specifically indicates open-ended inclusion in the so-described one or more listed features, elements in a combination, unless otherwise stated with limiting language. Furthermore, to the extent that the terms “includes,” “has,” “have,” “contains,” and other similar words are used in either the detailed description, such terms are intended to be inclusive in a manner similar to the term “comprising.”
[0029] In the following description, for the purposes of explanation, various specific details are set forth to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features.
[0030] The description provided herein discloses exemplary embodiments only and is not intended to limit the scope, applicability, or configuration of the present disclosure. Rather, the foregoing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing any of the exemplary embodiments. Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it may be understood by one of the ordinary skilled in the art that the embodiments disclosed herein may be practiced without these specific details.
[0031] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein the description, the singular forms "a", "an", and "the" include plural forms unless the context of the disclosure indicates otherwise.
[0032] The terminology and structure employed herein are for describing, teaching, and illuminating some embodiments and their specific features and elements and do not limit, restrict, or reduce the scope of the present disclosure. Accordingly, unless otherwise defined, all terms, and especially any technical and/or scientific terms, used herein may be taken to have the same meaning as commonly understood by one having ordinary skill in the art.
[0033] The various aspects including the example aspects are now described more fully with reference to the accompanying drawings, in which the various aspects of the disclosure are shown. The disclosure may, however, be embodied in different forms and should not be construed as limited to the aspects set forth herein. Rather, these aspects are provided so that this disclosure is thorough and complete, and fully conveys the scope of the disclosure to those skilled in the art. In the drawings, the sizes of components may be exaggerated for clarity.
[0034] Various aspects of the present disclosure to provide a system and a method for transmitting a message in a wireless communication network.
[0035] In another aspect of the present disclosure, the system and the method support message delivery between two user equipment irrespective of access domain and network interfaces using by utilizing a combined Home Subscriber Server-Home Location Register (HSS/HLR) to segregate different types of messages serving entities in a combined database.
[0036] In another aspect of the present disclosure, the system and the method provide optimized data management and improved network performance by reducing network traffic.
[0037] In the disclosure, various embodiments are described using terms used in some communication standards (e.g., 3rd Generation Partnership Project (3GPP), Extensible Radio Access Network (xRAN), and Open-Radio Access Network (O-RAN)), but these are merely examples for description. Various embodiments of the disclosure may also be easily modified and applied to other communication systems.
[0038] In order to facilitate an understanding of the disclosed invention, a number of terms are defined below.
[0039] The term ‘Short messaging entity (SME)’ in the present disclosure may refer to an entity which receives or sends short messages. The SME may be located in the fixed network, a mobile station, or another service center.
[0040] The term ‘Circuit Switched (CS) domain’ in the present disclosure may refer to a type of network configuration which comprise all network functionality for provision of bearer and teleservices in a circuit orientated manner. Circuit switching is a method of implementing a telecommunications network in which two network nodes establish a dedicated communications channel (circuit).
[0041] The term ‘Packet Switched (PS) domain’ in the present disclosure may refer to a type of network configuration which comprise all network functionality for provision of bearers in a packet orientated manner. A packet-switched connection transports user information in the form of bit packets, where each packet can be routed independently from the others.
[0042] The term ‘Evolved Packet System (EPS)’ in the present disclosure may refer to a core network architecture which is capable of uniquely identifying each device that connects via different access networks.
[0043] The term ‘Internet Protocol Multimedia Subsystem (IMS)’ in the present disclosure may represent a standardized architectural framework for delivering multimedia communications services such as voice, video and text messaging over Internet Protocol (IP) networks.
[0044] The term ‘Message Service Centre (MSC)’ or ‘Short Message Service Center (SMSC)’ in the present disclosure may refer to a component of a mobile phone network that handles text message operations. The SMSC is responsible for receiving, storing, routing and forwarding Short Message Service (SMS) messages from mobile handsets.
[0045] The term ‘Internet Protocol Short Message Gateway (IP-SM-GW)’ in the present disclosure may refer to a component of the mobile phone network that provide the protocol interworking for delivery of the short message between the IP-based UE and the SC. The message is routed to the SC for delivery to the SMS-based user or the message is received from the SC of an SMS-based UE for delivery to an IP-based UE.
[0046] The term ‘SMS-internetworking Mobile Switching Center (SMS-IWMSC)’ in the present disclosure may refer to a component of the mobile phone network which acts as an interface between the Public Land and Mobile Network (PLMN) or Core Network (CN) and the SMSC to help short messages to be transferred from Mobile Stations to the SMSC.
[0047] The term ‘SMS-gateway Mobile Switching Center (SMS-GMSC)’ in the present disclosure may refer to a component of the mobile phone network which acts as a gateway and routing center for SMS messages within a mobile network, enabling the exchange of messages between mobile devices and external networks. The SMS-GMSC ensures efficient routing, interoperability, and delivery of SMS messages, contributing to seamless communication for mobile subscribers.
[0048] The term ‘Home Subscriber Server (HSS)’ in the present disclosure may refer to a centralized database for storing subscriber information and facilitating essential network operations. The HSS supports authentication, authorization and mobility management functions. The HSS is the main subscriber database which provides details of the subscribers to other entities within the network.
[0049] The term ‘Home Location Register (HLR)’ in the present disclosure may refer to a database that contains data regarding authorized subscribers using a Global System for Mobile Communication (GSM) core network. The HLR stores information ranging from phone numbers to current location of the subscriber. The HLR is a database of all active customers of a mobile network, including their number, service entitlement, and number porting history.
[0050] The term “Message Waiting Indication (MWI)” in the present disclosure may be a data to be stored in the HLR associated with the MSC indicating that there is one or more messages waiting in the MSC to be delivered to the UE (due to unsuccessful delivery attempt(s)).
[0051] The term “Message Waiting Data (MWD)” in the present disclosure may be a part of the MWI to be stored in the HLR. The MWD may comprises of an address list of the MSCs which have messages waiting to be delivered to the UE.
[0052] The term ‘Home Subscriber Server-Home Subscriber Register (HSS/HLR)’ in the present disclosure serves as a primary database repository of subscriber information within an access domain in a core network. The HSS/HLR allows the signaling to be separated from policy providing a streamlined, high performing network by centralizing all the subscriber information in a single place.
[0053] The term ‘Mobile Application Part (MAP) protocol’ in the present disclosure is an application layer protocol. The key function of the MAP protocol is to connect distributed switching elements in the core network such as providing interaction between the MSC and the HLR. The MAP protocol basically facilitates for subscriber data management, authentication, call handling, location management, SMS management and subscriber tracing. The major function of the MAP protocol is to handle mobility procedures such as passing information of a mobile subscriber from one switching area to another. The MAP protocol supports both circuit and packet switch domains.
[0054] The term ‘diameter’ in the present disclosure is a protocol that provides a basic framework for any kind of services which require Access, Authorization, and Accounting (AAA) or Policy support across many IP based networks. The diameter protocol supports only packet switch domain.
[0055] The present disclosure relates to a system and a method for supporting message delivery in transmitting the message in the wireless communication network. When a User Equipment (UE) of a sender transmits the message to the UE of a recipient, there are multiple processes involved in transmission. The message may be received by a Message Serving Center (MSC) node associated with the UE of the sender via a Base Station (BS). The MSC node may determine subscription of the UE of the recipient. If the UE of the recipient is subscribed to the same MSC node, then the MSC node may deliver the message from the UE of the sender to the UE of the recipient. When the UE of the recipient may not be available for receiving the message from the UE of the sender, the MSC node associated with the UE of the sender may store the message and may send the message to the UE of the recipient when it is available. The subscription of the recipient is authenticated and registered in the HSS/HLR. However, if the UE of the recipient is unavailable, not subscribed to the MSC and belong to different access domain, then the MSC may attempt to deliver the message through the network.
[0056] The present disclosure may utilize the combined HSS/HLR that may serve as the primary database repository of subscriber information within the network. The combined HSS/HLR may centralize all the subscriber information and may allow signaling based on at least one access domain. The combined HSS/HLR may provide convergence of subscription-related information, authentication, and subscriber location. To efficiently manage message delivery, the combined HSS/HLR may have a feature to segregate different types of messages serving entities in a combined database for the HSS/HLR and may serve as per a required access domain. The MSC associated with the UE of the sender may subscribe for an alert message to the combined HSS/HLR of the UE of the recipient to receive a notification on availability of the UE of the recipient for delivering the message.
[0057] The combined HSS/HLR may store an address of the MSC node in Message Waiting Data (MWD) in the combined database according to the at least one access domain. The combined HSS/HLR may trigger alert message to all the MSC in the list irrespective of the access domain. After receiving the alert message, the MSC associated with the UE of the sender may attempt to deliver the message to the UE of the recipient and the combined HSS/HLR may clear the MWD in the combined database. This may in turn optimize network traffic by attempting to deliver messages through the at least one access domain. Also, this may reduce inter-network traffic between HSS and HLR and may optimize data management in the combined database thereby enhancing performance of the network.
[0058] FIG. 1 illustrates a diagram depicting an environment of a wireless communication network 100, in accordance with an embodiment of the present disclosure.
[0059] The wireless communication network 100 includes coverage regions 106-1 to 106-N (hereinafter cumulatively referred to as the coverage region 106). The coverage region 106 is served by one or more Base Stations (BSs) 102-1 to 102-N. Each base station among the BSs 102-1 to 102-N may have same or similar configuration and may also be referred to as “BS 102” or “node 102”. The BSs 102-1 to 102-N serves one or more User Equipment (UEs) 104-1 to 104-N in the coverage region 106. Each user equipment among the UEs 104-1 to 104-N may have same or similar configuration and may also be referred to as “UE 104”. The BSs 102-1 to 102-N are connected to a network 108 to provide one or more services to the UEs 104-1 to 104-N. The wireless communication network 100 further includes a server 110 connected to the network 108. The server 110 is configured to execute data processing operations to support message delivery between two UEs among the UEs 104-1 to 104-N in the wireless communication network 100 irrespective of access domain and network interfaces. The server 110 may be hereinafter referred to as a combined Home Subscriber Server-Home Location Register (HSS/HLR).
[0060] The BS 102 may be at least one relay, and at least one Distributed Unit (DU). Typically, the BS 102 may be a network infrastructure that provides wireless access to one or more terminals. The BS 102 has coverage defined to be a predetermined geographic area based on the distance over which a signal may be transmitted. The BS 102 may be referred to as, in addition to “base station”, “access point (AP)”, “evolved NodeB (eNodeB or eNB)”, “5G node (5th generation node)”, “next generation NodeB (gNB)”, “wireless point”, “transmission/reception point (TRP)”, “Radio Access Network (RAN)” or other terms having equivalent technical meanings.
[0061] The UE 104 may be, at least one DU, at least one Mobile Termination (MT) unit, and at least one relay. Typically, the term “user equipment” or “UE” can refer to any component such as “mobile station”, “subscriber station”, “remote terminal”, “wireless terminal”, “receive point”, or “end user device”.
[0062] The network 108 may include suitable logic, circuitry, and interfaces that may be configured to provide several network ports and several communication channels for transmission and reception of data related to operations of various entities of the wireless communication network 100. Each network port may correspond to a virtual address (or a physical machine address) for transmission and reception of the communication data. For example, the virtual address may be an Internet Protocol Version 4 (IPV4) (or an IPV6 address) and the physical address may be a Media Access Control (MAC) address. The network 108 may be associated with an application layer for implementation of communication protocols based on one or more communication requests from the various entities of the wireless communication network 100.
[0063] The communication data may be transmitted or received via the communication protocols. Examples of the communication protocols may include, but are not limited to, Hypertext Transfer Protocol (HTTP), File Transfer Protocol (FTP), Simple Mail Transfer Protocol (SMTP), Domain Network System (DNS) protocol, Common Management Interface Protocol (CMIP), Transmission Control Protocol and Internet Protocol (TCP/IP), User Datagram Protocol (UDP), Long Term Evolution (LTE) communication protocols, or any combination thereof. In some aspects of the present disclosure, the communication data may be transmitted or received via at least one communication channel of several communication channels in the network 108. The communication channels may include, but are not limited to, a wireless channel, a wired channel, a combination of wireless and wired channel thereof. The wireless or wired channel may be associated with a data standard which may be defined by one of a Local Area Network (LAN), a Personal Area Network (PAN), a Wireless Local Area Network (WLAN), a Wireless Sensor Network (WSN), Wireless Area Network (WAN), Wireless Wide Area Network (WWAN), a metropolitan area network (MAN), a satellite network, the Internet, an optical fiber network, a coaxial cable network, an infrared (IR) network, a radio frequency (RF) network, and a combination thereof. Aspects of the present disclosure are intended to include or otherwise cover any type of communication channel, including known, related art, and/or later developed technologies.
[0064] The server 110 may be a network of computers, a software framework, or a combination thereof, that may provide a generalized approach to create a server implementation. Examples of the server 110 may include, but are not limited to, personal computers, laptops, mini-computers, mainframe computers, any non-transient and tangible machine that can execute a machine-readable code, cloud-based servers, distributed server networks, or a network of computer systems. The server 110 may be realized through various web-based technologies such as, but not limited to, a Java web-framework, a .NET framework, a personal home page (PHP) framework, or any web-application framework. In other aspects of the present disclosure, the server 110 may be configured to support the message delivery between the UEs 104-1 to 104-N in the wireless communication network 100.
[0065] FIG. 2 illustrates a block diagram of a system 200 for supporting message delivery in the wireless communication network 100, in accordance with an embodiment of the present disclosure. The system 200 may include a network 108, a group of wireless nodes 102 (collectively referred to as nodes 102) connected to the network 108, a group of UEs 104-1 to 104-N (collectively referred to as UE 104) connected to the network 108 via the group of wireless nodes 102, a message receiving entity 208 to receive messages from the UE 104, a Message Service Centre (MSC) 210, an Internet Protocol Short Message Gateway (IP-SM-GW) 212, a Short Message Service Center (SMSC)/ an SMS-internetworking Mobile Switching Center (SMS-IWMSC)/ and an SMS-gateway Mobile Switching Center (SMS-GMSC) 214, the combined Home Subscriber Server-Home Location Register (HSS/HLR) 110 (hereinafter may be referred to as “HSS/HLR 110” or “server 110”), and a combined database 216 for the HSS/HLR 110 (hereinafter may also be referred to as “database 216”). The UE 104-1 to 104-N may utilize the at least one access domain to communicate with the network 108. The at least one access domain may be at least one of Circuit Switched (CS), Packet Switched (PS), Evolved Packet System (EPS), and Internet Protocol Multimedia Subsystem (IMS). FIG. 2 shows a group of wireless nodes or BS 102 and a group of UE 104 to simplify the illustration as each BS among the BSs 102-1 to 102-N have same or similar configuration and each user equipment among the UEs 104-1 to 104-N have same or similar configuration.
[0066] The HSS/HLR 110 includes a communication interface 202, a processor 204, and a memory 206 coupled to the processor 204. The processor 204 may control the operation of the HSS/HLR 110 coupled to a Message Serving Center (MSC) node of the network 108. The MSC node may include one of the MSC 210/ the IP-SM-GW 212/ or the SMSC/SMS-IWMSC/SMS-GMSC 214. The processor 204 may also be referred to as a Central Processing Unit (CPU). The memory 206 may provide instructions and data to the processor 204 for performing functions of the HSS/HLR 110. The memory 206 may include a Random Access Memory (RAM), a Read-Only Memory (ROM) and a portion of the memory 206 may also include Non-Volatile Random Access Memory (NVRAM). The processor 204 may perform logical and arithmetic operations based on instructions stored within the memory 206. The communication interface 202 may allow transmission and reception of data between the HSS/HLR 110 and the network 108. The communication interface 202 may include a transmitter, a receiver, and a single or multiple transmitting antennas electrically coupled to the transmitter and the receiver of the communication interface 202.
[0067] The communication interface 202 may be configured to enable the HSS/HLR 110 to communicate with various entities of the system 200 via the network 108. Examples of the communication interface 202 may include, but are not limited to, a modem, a network interface such as an Ethernet card, a communication port, and/or a Personal Computer Memory Card International Association (PCMCIA) slot and card, an antenna, a radio frequency (RF) transceiver, one or more amplifiers, a coder-decoder (CODEC) chipset, a subscriber identity module (SIM) card, and a local buffer circuit. It will be apparent to a person of ordinary skill in the art that the communication interface 202 may include any device and/or apparatus capable of providing wireless or wired communications between the HSS/HLR 110 and various other entities of the system 200.
[0068] In some aspects of the present disclosure, the HSS/HLR 110 may be coupled to the database 216 that provides data storage space to the HSS/HLR 110. The database 216 may store information related to configuration parameters, details related to the nodes 102-1 to 102-N and other relevant information needed for the operation of the HSS/HLR 110. The database 216 may be accessed and updated by the HSS/HLR 110 as part of alert generation process. The database 216 may correspond to a centralized database system configured to store and manage structured data, such as network-related data and configurations. The database 216 may be a relational database organizing related data such as in a table, or a non-relational database organizing graphical and time series data.
[0069] The IP-SM-GW 212 may provide protocol interworking for delivery of the message between the IP-based UE and the SMSC 214. The SMSC 214 may receive, store, forward, and route messages from the UE 104 and other gateways. The SMS-IWMSC 214 may act as an interface between the Public Land and Mobile Network (PLMN) or Core Network and the SMSC 214 to help messages to be transferred from the UE 104 to the SMSC 214. The SMS-GMSC 214 may be used to route calls outside the network 108.
[0070] The processor 204 may include one or more general purpose processors and/or one or more special purpose processors, a microprocessor, a digital signal processor, an application specific integrated circuit, a microcontroller, a state machine, or ay any type of programmable logic array. The processors 204 may include may include an intelligent hardware device including a general-purpose processor, such as, for example, and without limitation, a Central Processing Unit (CPU), an Application Processor (AP), a dedicated processor, or the like, a graphics-only processing unit such as a Graphics Processing Unit (GPU), a microcontroller, a Field-Programmable Gate Array (FPGA), a programmable logic device, a discrete hardware component, or any combination thereof. The processor 204 may be configured to execute computer-readable instructions stored in the memory 206 to cause the server 110 to perform various functions.
[0071] The memory 206 may further include, but not limited to, non-transitory machine-readable storage devices such as hard drives, magnetic tape, floppy diskettes, optical disks, compact disc read-Only Memories (CD-ROMs), and magneto-optical disks, semiconductor memories, such as ROMs, RAMS, programmable read-only memories PROMs), erasable PROMs (EPROMs), electrically erasable PROMs (EEPROMs), flash memory, magnetic or optical cards, or other type of media/machine-readable medium suitable for storing electronic instructions.
[0072] In addition, the memory may, in some examples, be considered a non-transitory storage medium. The "non-transitory" storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted as the memory is non-movable. In some examples, the memory may be configured to store larger amounts of information. 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 may be an internal storage unit or an external storage unit of the server, cloud storage, or any other type of external storage.
[0073] Embodiments of the present technology may be described herein with reference to flowchart illustrations of methods and systems according to embodiments of the technology, and/or procedures, algorithms, steps, operations, formulae, or other computational depictions, which may also be implemented as computer program products. In this regard, each block or step of the flowchart, and combinations of blocks (and/or steps) in the flowchart, as well as any procedure, algorithm, step, operation, formula, or computational depiction can be implemented by various means, such as hardware, firmware, and/or software including one or more computer program instructions embodied in computer-readable program code. As will be appreciated, any such computer program instructions may be executed by one or more computer processors, including without limitation a general-purpose computer or special purpose computer, or other programmable processing apparatus to perform a group of operations comprising the operations or blocks described in connection with the disclosed methods.
[0074] Further, these computer program instructions, such as embodied in computer-readable program code, may also be stored in one or more computer-readable memory or memory devices (for example, the memory 206) that can direct a computer processor or other programmable processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory or memory devices produce an article of manufacture including instruction means which implement the function specified in the block(s) of the flowchart(s).
[0075] It will further be appreciated that the term “computer program instructions” as used herein refer to one or more instructions that can be executed by the one or more processors (for example, the processor 204) to perform one or more functions as described herein. The instructions may also be stored remotely such as on a server, or all or a portion of the instructions can be stored locally and remotely.
[0076] Although FIG. 1 and FIG. 2 illustrate one example of the system 100, various changes may be made to FIG. 1 and FIG. 2. For example, the system 100 may include any number of user devices in any suitable arrangement. Further, in another example, the HSS/HLR 110 may include any number of components in addition to the components shown in FIG. 2. Further, various components in FIG. 1 and FIG. 2 may be combined, further subdivided, or omitted and additional components may be added according to particular needs.
[0077] In one embodiment of the present disclosure, a UE 104-1 among the UEs 104-1 to 104-N (may also be referred to as “first UE”) may send a message to a UE 104-N among the UEs 104-1 to 104-N (may also be referred to as “second UE”) via the network 108. Depending on the at least one access domain of the UE 104-1, the MSC node associated with the UE 104-1 may determine the subscription and availability of the UE 104-N. If the UE 104-N may not be subscribed or may not be available to receive the message from the UE 104-1, then the MSC node associated with the UE 104-1 may subscribe to an alert message with the HSS/HLR 110.
[0078] In some aspects of the present disclosure, the processor 204 of the HSS/HLR 110 may comprise one or more modules such as, a reception module 218, a subscription module 220, a storage module 222, a determination module 224, and a transmission module 226. The reception module 218 of the HSS/HLR 110 may receive a subscription request for the alert message from the MSC node associated with the UE 104-1. The subscription module 220 may subscribe MSC node associated with the UE 104-1 for the alert message. The storage module 216 may store a Message Waiting Data (MWD) in the combined database 216 of HSS/HLR 110. The reception module 218 may receive a subscriber attach request from the UE 104-N via a MSC node associated with the UE 104-N. The determination module 224 may determine whether the UE 104-N is available. The transmission module 226 may transmit the alert message to the MSC node associated with the UE 104-1 to initiate delivery of the message from the UE 104-1 to the UE 104-N.
[0079] The storage module 222 of the HSS/HLR 110 may store the MWD comprising address of the MSC node associated with the UE 104-1. The MWD may also comprise a failure reason for the message undelivered to the UE 104-N. The failure reason may indicate either the UE 104-N may be unavailable due to connectivity issues or may be unavailable due to memory issues. The memory issues may arise if a message storing memory of the UE 104-N may be full and space for storing new messages is unavailable. The connectivity issues may arise if the UE 104-N may not be in the coverage region 106 of the network 108. The UE 104-N may be switched off due to power outage and may be unavailable to receive the message from the UE 104-1.
[0080] The determination module 224 may determine the subscription of the UE 104-N and the availability of the UE 104-N. The transmission module 226 may transmit the alert message to the MSC node associated with the UE 104-1 upon determining the availability of the UE 104-N. The MSC node associated with the UE 104-1 may forward the message from the UE104-1 to the UE 104-N.
[0081] FIG. 3 illustrates a process flow diagram depicting a method 300 for supporting message delivery between two user equipment in the wireless communication network 100, in accordance with an embodiment of the present disclosure. The method 300 comprises a series of operation steps indicated by blocks 302 through 322.
[0082] At block 302, the message receiving entity 208 may receive the message from the UE 104-1. The message receiving entity 208 may be the SME present in the BS 102. If the UE 104-1 uses the CS access domain, the MSC 210 may receive the message from the message receiving entity 208. If the UE 104-1 uses the IMS access domain, the IP-SM-GW 212 may receive the message from the message receiving entity 208. If the UE 104-1 uses the EPS access domain, the SMSC/SMS-IWMSC/SMS-GMSC 214 may receive the message from the message receiving entity 208.
[0083] At block 304, subscription of the UE 104-N may be determined by the MSC node associated with the UE 104-1 based on the at least one access domain utilized by the UE 104-1.
[0084] At block 306, the MSC node associated with the UE 104-1 may subscribe to the HSS/HLR 110 for receiving the alert message and may check the HSS/HLR 110 for subscription of the UE 104-N. The MSC node associated with the UE 104-1 may store the message from the UE 104-1.
[0085] At block 308, the HSS/HLR 110 may store the address of the MSC node associated with the UE 104-1 comprising the message from the UE 104-1 to be delivered to the UE 104-N in the Message Waiting Data (MWD) of the combined database 216.
[0086] At block 310, the HSS/HLR 110 may receive the subscriber attach request from the MSC node associated with the UE 104-N in the corresponding access domain.
[0087] At block 312, the HSS/HLR 110 may check the MWD for responding to the subscriber attach request with respect to the MSC node associated with the UE 104-N.
[0088] At block 314, the HSS/HLR 110 may check for the subscription of the UE 104-N in the combined database 216 for receiving alert message when the UE 104-N may not be reachable by the MSC node associated with the UE 104-1.
[0089] At block 316, the HSS/HLR 110 may send the alert message to the MSC node associated with the UE 104-1 based on the MWD of the combined database 216 to initiate delivery of the message to the UE 104-N and may clear the MWD of the combined database 216.
[0090] At block 318, the MSC node associated with the UE 104-1 may receive the alert message from the HSS/HLR 110 and may attempt to deliver the message from the UE 104-1 to the UE 104-N.
[0091] At block 320, if the UE 104-N is subscribed to the HSS/HLR 110 and reachable, the node associated with the UE 104-1may deliver the message from the UE 104-1 to the UE 104-N.
[0092] At block 322, the UE 104-N may successfully receive the message from the UE 104-1 and the method 300 terminates.
[0093] In one aspect, the HSS/HLR 110 may perform conversion of network communication protocol. The protocol may be at least one of the MAP protocol, the diameter protocol, and a MAP-diameter protocol. The MAP protocol may allow implementation of mobile network signaling infrastructure and the diameter protocol may provide an Authentication, Authorization and Accounting (AAA) framework for applications such as network access or IP mobility. The MSC 210 may communicate with the HSS/HLR 110 based on the MAP protocol. The IP-SM-GW 212 may communicate with the HSS/HLR 110 based on the diameter protocol. The SMSC/SMS-IWMSC/SMS-GMSC 214 may communicate with the HSS/HLR 110 based on the MAP-diameter protocol.
[0094] In one aspect, the HSS/HLR 110 may segregate the MWD based on the at least one access domain of the MSC 210, the IP-SM-GW 212, and the SMSC/SMS-IWMSC/SMS-GMSC 214.
[0095] FIG. 4 illustrates a process flow diagram depicting a method 400 for transmitting the message in the wireless communication network 100, in accordance with an embodiment of the present disclosure. The method 400 comprises a series of operation steps indicated by blocks 402 through 412.
[0096] At block 402, the processor 204 may receive a subscription request for an alert message from the MSC node associated with a first UE 104-1.
[0097] In some aspects of the present disclosure, each of the MSC node associated with the first UE 104-1 and the MSC node associated with the second UE 104-N may be at least one of the MSC 210/ the IP-SM-GW 212/ the SMSC/SMS-IWMSC/SMS-GMSC 214.
[0098] At block 404, the processor 204 may subscribe, based on the reception of the subscription request, the MSC node associated with the first UE 104-1 for the alert message. The MSC node associated with the first UE 104-1 may subscribe to the alert message upon determining that the second UE 104-N is unavailable to receive the message from the first UE 104-1.
[0099] At block 406, the processor 204 may store the MWD in the combined database 216 of the HSS/HLR 110. The MWD comprises an address of the MSC node associated with the first UE 104-1 and the failure reason indicating that the second UE 104-N is unavailable.
[0100] At block 408, the processor 204 may receive, the subscriber attach request from the second UE via the MSC node associated with the second UE 104-N.
[0101] At block 410, the processor 204 may determine, based on the subscriber attach request from the second UE 104-N, whether the second UE 104-N is available. Further, the processor 204 may determine whether the second UE 104-N is subscribed to the HSS/HLR 110. The second UE 104-N may be attached to the at least one access domain.
[0102] In some aspects of the present disclosure, the at least one access domain may be at least one of the CS, the PS, the EPS, and the IMS.
[0103] Furthermore, the processor 204 may determine, upon determining that the second UE 104-N is attached to the at least one access domain, whether the MSC node associated with the first UE 104-1 is subscribed to receive the alert message based on the MWD.
[0104] At block 412, the processor 204 may transmit, based on the MWD, the alert message to the MSC node associated with the first UE 104-1 to initiate delivery of the message from the first UE 104-1 to the second UE 104-N.
[0105] In some aspects of the present disclosure, the MSC node associated with the first UE 104-1 may transmit the message to the second UE 104-N based on the reception of the alert message from the HSS/HLR 110 indicating the availability of the second UE 104-N.
[0106] In some aspects of the present disclosure, the HSS/HLR 110 may support the MAP protocol and the diameter protocol for signaling in the at least one access domain. The HSS/HLR 110 may store the MWD data received via an interface using the MAP protocol separately from the MWD data received via an interface using the diameter protocol.
[0107] Referring to the technical abilities and advantageous effect of the present disclosure, operational advantages that may be provided by above disclosed system and method may support message delivery in the wireless communication network for improving the quality of service of the network. Another potential advantage of the one or more embodiments may include supporting message delivery between two user equipment irrespective of access domain and network interfaces by utilizing the combined HSS/HLR to segregate different type of message serving entities in the combined database. This in turn optimizes data management of the network and improves network performance by reducing network traffic.
[0108] Those skilled in the art will appreciate that the methodology described herein in the present disclosure may be carried out in other specific ways than those set forth herein in the above disclosed embodiments without departing from essential characteristics and features of the present disclosure. The above-described embodiments are therefore to be construed in all aspects as illustrative and not restrictive.
[0109] 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. For example, orders of processes described herein may be changed and are not limited to the manner described herein. Any combination of the above features and functionalities may be used in accordance with one or more embodiments.
[0110] In the present disclosure, each of the embodiments has been described with reference to numerous specific details which may vary from embodiment to embodiment. The foregoing description of the specific embodiments disclosed herein may reveal the general nature of the embodiments herein that others may, 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 are intended to be comprehended within the meaning of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and is not limited in scope.
LIST OF REFERENCE NUMERALS
[0111] The following list is provided for convenience and in support of the drawing figures and as part of the text of the specification, which describe innovations by reference to multiple items. Items not listed here may nonetheless be part of a given embodiment. For better legibility of the text, a given reference number is recited near some, but not all, recitations of the referenced item in the text. The same reference number may be used with reference to different examples or different instances of a given item. The list of reference numerals is:
100 - Wireless communication network
102 - Base Station (BS)
102-1 to 102-N - One or more BSs
104 - User Equipment (UE)
104-1 to 104-N - One or more UEs
106-1 to 106-N - Coverage region
108 - Network
110 - Server/ Home Subscriber Server-Home Location Register (HSS/HLR)
200 -Block Diagram of the system for supporting message delivery
202 - Communication interface of the HSS/HLR 110
204 - Processor of the HSS/HLR 110
206 - Memory of the HSS/HLR 110
208 - Message receiving entity
210 - Message Service Centre (MSC)
212 - Internet Protocol Short Message Gateway (IP-SM-GW)
214 - Short Message Service Center (SMSC), SMS-internetworking Mobile Switching Center (SMS-IWMSC), and SMS-gateway Mobile Switching Center (SMS-GMSC)
216 - Combined database for the HSS/HLR 110
218 - Reception module
220 - Subscription module
222 - Storage module
224 - Determination module
226 - Transmission module
300 - Process flow diagram for supporting message delivery
302- 322- Operation steps of the process flow diagram 300
400 - Method for transmitting the message
402-412 - Operation steps of the method 400
,CLAIMS:We Claim:

1. A method (400) for transmitting a message in a communication network, the method (400) comprising:
receiving (402), by a reception module (218) of a server (110) from a Message Serving Center (MSC) node associated with a first User Equipment (UE), a subscription request for an alert message;
subscribing (404), by a subscription module (220) of the server (110) based on the reception of the subscription request, the MSC node associated with the first UE (104-1) for the alert message;
storing (406), by a storage module (222) of the server (110), a Message Waiting Data (MWD) in a database (216) of the server (110);
receiving (408), by the reception module (218) from a MSC node associated with a second UE (104-N), a subscriber attach request from the second UE (104-N);
determining (410), by a determination module (224) of the server (110) based on the subscriber attach request from the second UE (104-N), whether the second UE (104-N) is available; and
transmitting (412), by a transmission module (226) of the server (110) based on the MWD, the alert message to the MSC node associated with the first UE (104-1) to initiate delivery of the message from the first UE (104-1) to the second UE (104-N).

2. The method (400) as claimed in claim 1, wherein the MSC node associated with the first UE (104-1) subscribes to the alert message upon determining that the second UE (104-N) is unavailable to receive the message from the first UE (104-1).

3. The method (400) as claimed in claim 1, wherein the MSC node associated with the first UE (104-1) transmits the message to the second UE (104-N) based on a reception of the alert message.

4. The method (400) as claimed in claim 1, further comprising determining, by the determination module (224), whether the second UE (104-N) is subscribed to the server (110), wherein the second UE (104-N) is attached to at least one access domain.

5. The method (400) as claimed in claim 4, further comprising determining, by the determination module (224) upon determining that the second UE (104-N) is attached to the at least one access domain, whether the MSC node associated with of the first UE (104-1) is subscribed to receive the alert message based on the MWD.

6. The method (400) as claimed in claim 4, wherein the at least one access domain is at least one of Circuit Switched (CS), Packet Switched (PS), Evolved Packet System (EPS), and Internet Protocol Multimedia Subsystem (IMS).

7. The method (400) as claimed in claim 1, wherein each of the MSC node associated with the first UE (104-1) and the MSC node associated with the second UE (104-N) is at least one of Message Service Centre (MSC), Internet Protocol Short Message Gateway (IP-SM-GW), Short Message Service Center (SMSC), SMS-Internetworking Mobile Switching Center (SMS-IWMSC), and SMS-Gateway Mobile Switching Center (SMS-GMSC).

8. The method (400) as claimed in claim 1, wherein the MWD comprises an address of the MSC node associated with the first UE (104-1) and a failure reason indicating that the second UE (104-N) is unavailable.

9. The method (400) as claimed in claim 1, wherein the server (110) supports a Mobile Application Part (MAP) protocol and a diameter protocol for signaling in the at least one access domain.

10. The method (400) as claimed in claim 9, wherein the server (110) stores the MWD received via an interface using the MAP protocol separately from the MWD received via an interface using the diameter protocol.

11. A system (200) for transmitting a message in a communication network, the system (200) comprising:
a reception module (218) configured to receive, from a Message Serving Center (MSC) node associated with a first User Equipment (UE), a subscription request for an alert message;
a subscription module (220) configured to subscribe, based on the reception of the subscription request, the MSC node associated with the first UE (104-1) for the alert message;
a storage module (222) configured to store a Message Waiting Data (MWD) in a database (216) of a server (110);
the reception module (218) configured to receive, from a MSC node associated with a second UE (104-N), a subscriber attach request from the second UE (104-N);
a determination module (224) configured to determine, based on the subscriber attach request from the second UE (104-N), whether the second UE (104-N) is available; and
a transmission module (226) configured to transmit, based on the MWD, the alert message to the MSC node associated with the first UE (104-1) to initiate delivery of the message from the first UE (104-1) to the second UE (104-N).

12. The system (200) as claimed in claim 11, wherein the MSC node associated with the first UE (104-1) subscribes to the alert message upon determining that the second UE (104-N) is unavailable to receive the message from the first UE (104-1).

13. The system (200) as claimed in claim 11, wherein the MSC node associated with the first UE (104-1) transmits the message to the second UE (104-N) based on the reception of the alert message.

14. The system (200) as claimed in claim 11, wherein the determination module (224) is further configured to determine whether the second UE (104-N) is subscribed to the server (110), wherein the second UE (104-N) is attached to at least one access domain.

15. The system (200) as claimed in claim 14, wherein the determination module (224) is further configured to determine, upon determining that the second UE (104-N) is attached to the at least one access domain, whether the MSC node associated with the first UE (104-1) is subscribed to receive the alert message based on the MWD.

16. The system (200) as claimed in claim 14, wherein the at least one access domain is at least one of Circuit Switched (CS), Packet Switched (PS), Evolved Packet System (EPS), and Internet Protocol Multimedia Subsystem (IMS).

17. The system (200) as claimed in claim 11, wherein each of the MSC node associated with the first UE (104-1) and the MSC node associated with the second UE (104-N) is at least one of Message Service Centre (MSC), Internet Protocol Short Message Gateway (IP-SM-GW), Short Message Service Center (SMSC), SMS-Internetworking Mobile Switching Center (SMS-IWMSC), and SMS-Gateway Mobile Switching Center (SMS-GMSC).

18. The system (200) as claimed in claim 11, wherein the MWD comprises an address of the MSC node associated with the first UE (104-1) and a failure reason indicating that the second UE (104-N) is unavailable.

19. The system (200) as claimed in claim 11, wherein the server (110) supports a Mobile Application Part (MAP) protocol and a Diameter protocol for signaling in the at least one access domain.

20. The system (200) as claimed in claim 11, wherein the server (110) stores the MWD received via an interface using the MAP protocol separately from the MWD received via an interface using the Diameter protocol.