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 BARRING OF 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 to barring of services on a cellular device, more particularly relates to method and system for barring of Short Message Service (SMS) for the cellular device.
BACKGROUND OF THE INVENTION
[0002] Short Message/Messaging Service, commonly abbreviated as SMS, is a text messaging service component of most telephones, internet, and mobile device systems. It uses standardized communication protocols that let mobile devices exchange short text messages.
[0003] In SMS over IP Multimedia Subsystem (IMS) communication, SMS is encapsulated in a Session Initiation Protocol (SIP) message and carried over IMS core network to Short Message Service Center (SMSC). The IP Short Messaging Gateway (IPSM-GW) network element provides the interconnection between Global System for Mobile Communications-Universal Mobile Telecommunications System (GSM-UMTS) network and Long-Term Evolution-Evolved Packet Core (LTE-EPC) network for sending and receiving SMSs.
[0004] Call and text barring is an action that prevents numbers from being called or texted. This can also be used to stop receiving calls and texts.
[0005] In certain cases, to comply with regulatory requirements, it might be necessary to restrict messaging services in specific areas according to government directives. It is crucial to ensure that no messages are allowed to pass through those designated areas.
[0006] In the case of Long-Term Evolution (LTE) latched users, the cell- Identifier (cell-ID) is readily received in message or acknowledgement (ACK) headers. However, for Wireless Fidelity (Wi-Fi) latched users, the Wireless Local Area Network- Identifier (WLAN ID) is received instead of the cell-ID. Cell-ID information is required for SMS barring in any area, and the absence of this information can result in the failure of SMS barring for Wi-Fi users.

[0007] In the usual scenario, when a user is connected to an LTE network, we rely on the information received in message headers to retrieve the user's precise location.
However, this capability is not available for non-3GPP network such as WLAN. When it is necessary to terminate a message sent to a receiving party, knowing the user's location is essential to enable the service. In a known solution, a welcome message (Type 0 with PID 64) is sent to the device, and its response is used to obtain the location information. Unfortunately, for Wi-Fi users, neither of these messages contains accurate location information.

[0008] Therefore, there is a need for a method and a system in the art which is able to know, determine and report the exact location of cell phone users connected to a Wi-Fi network for implementing location-based barring of services efficiently such as SMS services.
SUMMARY OF THE INVENTION
[0009] One or more embodiments of the present disclosure provide a method and a system for barring of short message service (SMS).
[0010] In one aspect of the present invention, the system for barring of the short message service (SMS) is disclosed. The system includes an interface unit configured to receive the SMS from a user equipment (UE). The system further includes an identifier unit configured to determine a Radio Access Technology (RAT) type of the received SMS. The system further includes a retrieval unit configured to retrieve information pertaining to location of the UE from a Home Subscriber Server (HSS) when the RAT type is determined as a Wireless Local Area Network (WLAN) type. The system further includes a comparison unit configured to compare the retrieved information associated with the UE with a barred list to determine if the retrieved location is present in the barred list. The system further includes a transmittal unit configured to transmit an error code in response to determination of presence of the location in the barred list.
[0011] In an embodiment, the comparison unit is configured to map the retrieved location of the UE to a barred location in the barred list and in response to mapping of the location, map, a cell ID of the UE to a barred cell ID in the barred list.
[0012] In an embodiment, the identifier unit is further configured to parse a P-Access-Network-Info (PANI) header received along with the SMS to identify the RAT type and transmit a type 0 message to retrieve a PANI header, the PANI header is subsequently parsed to identify the RAT type.
[0013] In an embodiment, the retrieval unit is further configured to transmit a User Data Request (UDR) message to one of an Access and Mobility Management Function (AMF) and a Mobile Management Entity (MME) via the HSS to retrieve the information pertaining to the location of the UE and the cell ID of the UE.
[0014] In an embodiment, if, one of, the information pertaining to the location is not retrieved from the HSS and a negative response is received from the HSS, the one or more processor is configured to transmit the error code to the UE.
[0015] In an embodiment, the barred list includes one of, a location and a list of cell IDs within the location that are to be barred from at least transmitting SMS to or receiving SMS from other UEs.
[0016] In another aspect of the present invention, the method for barring of the short message service (SMS) is disclosed. The method includes the step of receiving the SMS from the UE. The method further includes the step of determining the RAT type of the received SMS. The method further includes the step of retrieving information pertaining to location of the UE from the HSS when the RAT type is determined as the WLAN type. The method further includes the step of comparing the retrieved information associated with the UE with the barred list to determine if the retrieved location is present in the barred list. The method further includes the step of transmitting the error code in response to determination of presence of the location in the barred list.
[0017] In another aspect of the invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions is disclosed. The computer-readable instructions are executed by a processor. The processor is configured to receive the SMS from the UE. The processor is further configured to determine the RAT type of the received SMS. The processor is further configured to retrieve information pertaining to location of the UE from the HSS when the RAT type is determined as WLAN type. The processor is further configured to compare the retrieved information associated with the UE with the barred list to determine if the retrieved location is present in the barred list. The processor is further configured to transmit the error code in response to determination of presence of the location in the barred list.
[0018] In another aspect of invention, a User Equipment (UE) is disclosed. The UE includes one or more primary processors communicatively coupled to one or more processors, the one or more primary processors coupled with a memory. The processor is configured to receive a short message service (SMS) from the UE. Thereafter, the one or more processors is configured to perform the method of barring the SMS.
[0019] 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
[0020] 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.
[0021] FIG. 1 is an exemplary block diagram of an environment for barring of Short Message Service (SMS), according to one or more embodiments of the present invention;
[0022] FIG. 2 an exemplary block diagram of a system for barring of SMS, according to one or more embodiments of the present invention;
[0023] FIG. 3 is a schematic representation of a workflow of the system of FIG. 1, according to the one or more embodiments of the present invention;
[0024] FIG. 4 is an exemplary block diagram of an architecture of the system of the FIG. 2, according to one or more embodiments of the present invention;
[0025] FIG. 5 is a signal flow diagram for barring of SMS according to one or more embodiments of the present invention; and
[0026] FIG. 6 is a schematic representation of a method for barring of SMS, according to one or more embodiments of the present invention.
[0027] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0028] 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.
[0029] 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.
[0030] 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.
[0031] The present disclosure provides a solution for location-based barring of Short Message Service (SMS) service by determining the exact location of a User Equipment (UE). In order to do the same, an IP Short Message Gateway (IPSMGW) transmits a location information query to the Home Subscriber Server (HSS). The HSS can retrieve the real-time user location from an MME (Mobility Management Entity) or an AMF (Access and Mobility Management Function) and provide a (cell – Identifier) cell-ID to the IPSMGW. The IPSMGW then compares the cell-ID information with the data available in the database, determining whether the message should be allowed or barred based on the information.
[0032] FIG. 1 illustrates an exemplary block diagram of an environment 100 for barring of Short Message Service (SMS), according to one or more embodiments of the present disclosure. In this regard, the environment 100 includes a User Equipment (UE) 102, a server 104, a network 106 and a system 108 communicably coupled to each other for barring of the SMS. The UE 102 aids a user to interact with the system 108 for transmitting the SMS.
[0033] As per the illustrated embodiment and for the purpose of description and illustration, the UE 102 includes, but not limited to, a first UE 102a, a second UE 102b, and a third UE 102c, and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the UE 102 may include a plurality of UEs as per the requirement. For ease of reference, each of the first UE 102a, the second UE 102b, and the third UE 102c, will hereinafter be collectively and individually referred to as the “User Equipment (UE) 102”.
[0034] In an embodiment, the UE 102 is one of, but not limited to, any electrical, electronic, electro-mechanical or an equipment and 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.
[0035] The environment 100 includes the server 104 accessible via the network 106. The server 104 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 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 embodiment, the entity may include, but is not limited to, a vendor, a network operator, a company, an organization, a university, a lab facility, a business enterprise side, a defense facility side, or any other facility that provides service.
[0036] The 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 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.
[0037] The 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 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.
[0038] The environment 100 further includes the system 108 communicably coupled to the server 104 and the UE 102 via the network 106. The system 108 is configured to barring of the SMS. As per one or more embodiments, the system 108 is adapted to be embedded within the server 104 or embedded as an individual entity.
[0039] Operational and construction features of the system 108 will be explained in detail with respect to the following figures.
[0040] FIG. 2 is an exemplary block diagram of the system 108 for barring of SMS, according to one or more embodiments of the present invention.
[0041] As per the illustrated embodiment, the system 108 includes one or more processors 202, a memory 204, a user interface 206, and a database 208. For the purpose of description and explanation, the description will be explained with respect to one processor 202 and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the system 108 may include more than one processors 202 as per the requirement of the network 106. 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.
[0042] As per the illustrated embodiment, 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.
[0043] In an embodiment, the user interface 206 includes a variety of interfaces, for example, interfaces for a graphical user interface, a web user interface, a Command Line Interface (CLI), and the like. The user interface 206 facilitates communication of the system 108. In one embodiment, the user interface 206 provides a communication pathway for one or more components of the system 108. Examples of such components include, but are not limited to, the UE 102 and the database 208.
[0044] The database 208 is one of, but not limited to, a centralized database, a cloud-based database, a commercial database, an open-source database, a distributed database, an end-user database, a graphical database, a No-Structured Query Language (NoSQL) database, an object-oriented database, a personal database, an in-memory database, a document-based database, a time series database, a wide column database, a key value database, a search database, a cache databases, and so forth. The foregoing examples of database 208 types are non-limiting and may not be mutually exclusive e.g., a database can be both commercial and cloud-based, or both relational and open-source, etc.
[0045] In order for the system 108 for barring of SMS, the processor 202 includes one or more modules. In one embodiment, the one or more modules includes, but not limited to, an interface unit 210, an identifier unit 212, a retrieval unit 214, a comparison unit 216, and a transmittal unit 218 communicably coupled to each other for barring of SMS.
[0046] The interface unit 210, the identifier unit 212, the retrieval unit 214, the comparison unit 216, and the transmittal unit 218 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 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 electronic circuitry.
[0047] In one embodiment, the interface unit 210 is configured to receive the SMS from the user using the UE 102. The SMS is a communication protocol widely used in the networks 106 to exchange short text messages between the UE 102. The SMS operates on various network technologies like Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), and Long-Term Evolution (LTE), facilitating communication between users across different UE 102.
[0048] Upon receiving the SMS from the UE 102, the identifier unit 212 is configured to determine a Radio access Technology (RAT) type of the received SMS. The RAT refers to the underlying technology used by the UE 102 to connect to the network 106. The RAT types include, but are not limited to, Bluetooth, Wi-Fi, GSM (Global System for Mobile Communications), CDMA (Code Division Multiple Access), UMTS (Universal Mobile Telecommunications System), LTE (Long-Term Evolution), 5G NR (Fifth Generation New Radio).
[0049] The identifier unit 212 determines the RAT type of the received SMS by parsing a P-Access-Network-Info (PANI) header along with the SMS. The P-Access-Network-Info (PANI) header field contains a cell identifier or location identifier, which is subsequently mapped, potentially by the user using the UE 102, into a real location. The PANI header along with the SMS is parsed to identify the RAT type.
[0050] In one embodiment, for a Mobile Terminated (MT) Short Message Service (SMS), when the cell-ID is blocked in a Public Land Mobile Network (PLMN), the IPSMGW 402 fetches the cell-ID information from a MT user by transmitting a Type-0 message. In particular, the identifier unit 212 is configured to transmit the type 0 message to retrieve the PANI header. The PANI header is subsequently parsed to identify the RAT type.
[0051] The type 0 message indicates that the UE 102 must acknowledge receipt of the short message but shall discard its contents. More specifically, a mobile station shall be able to receive the type 0 message irrespective of availability of memory in a Subscriber Identity Module (SIM) or the UE 102 or not. The mobile station shall not indicate the receipt of the type 0 message to the user using the UE 102 and the short message shall neither be stored in the SIM nor the UE 102.
[0052] Upon determining the RAT type of the received SMS, the retrieval unit 214 is configured to retrieve information pertaining to the location of the UE 102 from a Home Subscriber Server (HSS) 420. The HSS 420 stores subscriber-related information and plays a role in the authentication, authorization, and management of subscribers. The key functions of the HSS 420 include, but are not limited to, subscriber data management, authentication and authorization, mobility management, subscriber management and interoperability.
[0053] The location of the UE 102 from the HSS 420 is retrieved when the RAT type is determined as a Wireless Local Area Network (WLAN) type. The WLAN type refers to the type of wireless network technology used for local wireless connectivity. The WLAN includes Wi-Fi networks, which are commonly deployed in homes, businesses, public spaces, and various other environments to provide wireless internet access.
[0054] To retrieve the location from the HSS 420 by the retrieving unit 214, a User Data Request (UDR) message is transmitted to one of an Access and Mobility Management Function (AMF) and a Mobile Management Entity (MME) via the HSS 420. The UDR is sent by a diameter client to a diameter server in order to request user data. The message format of the UDR is as follows:
< User-Data -Request > :: = < Diameter Header: 306, REQ, PXY, 16777217 >
< Session-Id >
[DRMP]
{Vendor-Specific-Application-Id}
{Auth-Session-State}
{Origin-Host}
{Origin-Realm}
[Destination-Host]
{Destination-Realm}
[Current-Location]
[0055] In particular, to fetch the current location from the HSS 420, IP Short Message Gateway (IPSMGW) 402 (explained in FIG. 4) transmits the UDR message with Data Reference Attribute Value Pair (AVP), Current-Location AVP and Requested-Nodes AVP. The data reference AVP indicates the type of the requested user data in the operation UDR such as LocationInformation. The current-location AVP indicates whether an active location retrieval has to be initiated or not:
DoNotNeedInitiateActiveLocationRetrieva - the request indicates that the initiation of an active location retrieval is not required.
InitiateActiveLocationRetrieval -it is requested that an active location retrieval is initiated.
[0056] In an embodiment, the Requested-Nodes AVP is of type Unsigned32 and shall contain a bit mask. The meaning of the bits shall be as defined in the below table:
Bit Name Description
0 MME The requested data apply to the MME
3 AMF The requested data apply to the AMF (for 3GPP access)

[0057] For 4G users, in User Data Answer (UDA), the HSS 420 sends the EPSLocationInformation in Sh data xml. The Cell- Identifier (Cell-ID) is encoded in Base64 Format. IP Short Message (IPSM) should decode it and block accordingly. The UDA is sent by a server in response to the User-Data-Request command. The message format of the UDA is as follows:
Message Format :
< User-Data-Answer > ::= < Diameter Header: 306, PXY, 16777217 >
< Session-Id >
[ DRMP]
{Vendor-Specific-Application-Id}
[ Result-Code]
[Experimental-Result]
{Auth-Session-State}
{Origin-Host}
{Origin-Realm}
*[Supported-Features]
[Wildcarded-Public-Identity]
[Wildcarded-IMPU]
[User-Data]
[OC-Supported-Features]
[OC-OLR]
*[Load]
*[AVP]
[Failed-AVP]
*[Proxy-Info]
[0058] For 5G users, in UDA, HSS 420 sends the Sh-5GSLocationInformation in Sh xml. The Cell-ID is of the format < New radio Cell Global Identity (NCGI)>. It is received in plain format and IPSM should block it accordingly.
[0059] In an embodiment, if, one of, the information pertaining to the location is not retrieved from the HSS 420 then a negative response is received from the HSS. Upon receiving the negative response form the HSS 420, the retrieval unit 214 is configured to transmit the error code to the UE 102.
[0060] Upon retrieving the information pertaining to location of the UE 102 from the HSS 420, the comparing unit 216 is configured to compare the retrieved information associated with the UE 102 with a barred list. The barred list includes one of, a location and a list of cell IDs within the location that are to be barred from transmitting SMS to other UEs 102. The retrieved information associated with the UE 102 with the barred list to determine if the retrieved location is present in the barred list.
[0061] Further, the comparing unit 216 compares the retrieved information associated with the UE 102 with the barred list by mapping the retrieved location of the UE 102 to a barred location in the barred list. The barred location is a geographical area where a specific user or group of users is not permitted to access the network 106. In response to mapping of the location, the cell ID of the UE 102 is mapped with a barred cell ID in the barred list.
[0062] Upon comparing the retrieved information associated with the UE 102, the transmittal unit 218 is configured to transmit an error code in response to determination of presence of the location in the barred list. By doing so, irrespective of the network connection, the system 108 is configured to bar the SMS service at the location at which the SMS services have been barred for subscribers, thereby ensuring the intended security is not breached.
[0063] FIG. 3 describes a preferred embodiment of the system 108 of FIG. 2, according to various embodiments of the present invention. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the first UE 102a 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.
[0064] As mentioned earlier in FIG. 1, each of the first UE 102a the second UE 102b, and the third UE 102c may include an external storage device, a bus, a main memory, a read-only memory, a mass storage device, communication port(s), and a processor. The exemplary embodiment as illustrated in FIG. 3 will be explained with respect to the first UE 102a without deviating from the scope of the present disclosure and the limiting the scope of the present disclosure. The first UE 102a includes one or more primary processors 302 communicably coupled to the one or more processors 202 of the system 108.
[0065] The one or more primary processors 302 are coupled with a memory unit 304 storing instructions which are executed by the one or more primary processors 302. Execution of the stored instructions by the one or more primary processors 302 enables the first UE 102a to transmit the SMS to the one or mor processors 202.
[0066] As mentioned earlier in FIG. 2, the one or more processors 202 of the system 108 is configured for barring of SMS. As per the illustrated embodiment, the system 108 includes the one or more processors 202, the memory 204, the user interface 206, and the database 208. The operations and functions of the one or more processors 202, the memory 204, the user interface 206, and the database 208 are already explained in FIG. 2. For the sake of brevity, a similar description related to the working and operation of the system 108 as illustrated in FIG. 2 has been omitted to avoid repetition.
[0067] Further, the processor 202 includes the transceiver 210, the initiating unit 212, the determination unit 214, the creating unit 216, the dynamic activator unit 218 and the invoking unit 220. The operations and functions of the interface unit 210, the identifier unit 212, the retrieval unit 214, the comparison unit 216, and the transmittal unit 218 are already explained in FIG. 2. Hence, for the sake of brevity, a similar description related to the working and operation of the system 108 as illustrated in FIG. 2 has been omitted to avoid repetition. The limited description provided for the system 108 in FIG. 3, should be read with the description as provided for the system 108 in the FIG. 2 above, and should not be construed as limiting the scope of the present disclosure.
[0068] FIG. 4 is an exemplary block diagram of an architecture 400 of the system 108 for barring of the SMS, according to one or more embodiments of the present invention.
[0069] The architecture 400 includes an IPSMGW 402, which is communicably coupled with a Serving- Call Session Control Function (S-CSCF) 404, a F5 Load Balancer 406a and 406b, a Diameter Routing Agent (DRA) 408, a Signaling Transfer Point (STP) 410, an Element Management System (EMS) 412, and the database 208.
[0070] In an embodiment, the IPSMGW 402 system integrates with the S-CSCF 404 through Integrated Small Cell (ISC) over Session Initiation Protocol (SIP) interface. The ISC interface connects the S-CSCF 404 and Application Server(s). The S-CSCF 404 will trigger the IPSMGW 402 for 3rd Party Registrations and for forwarding SMS originated from the UE 102 towards the IPSMGW 402.
[0071] Upon transmitting the SMS from the UE 102, the IPSMGW 402 performs a Mobile Number Portability (MNP) 416 query by using a Session Initiation Protocol (SIP) MESSAGE method to find (Routable Number) RN and outbound Mobile Numbers. The MNP 416 server shall respond back with 302- Redirect, CONTACT header of the response shall contain the Location Routing Number (LRN) and domain info as required. This integration is done via the F5 load balancer 406b.
[0072] Thereafter, the IPSMGW 402 connects to an Online Charging System (OCS) 418, to provide diameter-based IMS online charging. This interface is via the Diameter Routing Agent (DRA) 408. Charging for pre-paid and post-paid subscribers will be via the OCS 418.
[0073] The IPSMGW 402 will communicate with the HSS 420 over Sh interface to fetch user registration data. The IPSMGW 402 integrates with CP (content provider) over Short Message Peer to Peer Protocol (SMPP) interface for Peer-to-Application (P2A) or Application-to-Peer (A2P) SMS service. This integration is done via the F5 load balancer 406a.
[0074] The IPSMGW 402 deployed for A2P traffic connects with P2P IPSMGW over SMPP interface to transfer SMPP request from the UE 102 to A2P IPSMGW. This integration is done via the F5 load balancer 406a. The IPSMGW 402 connects with a Service Capability Exposure Function (SCEF) 422 over T4 interface to receive device trigger messages. The IPSMGW 402 connects with the HSS 420 over S6c interface to fetch terminating the IPSMGW 420 address of user. The IPSMGW 420 connects with MME 424 over SGd interface to terminate the device trigger message to user. The front end of the IPSMGW 402 connects with a Home Location Register (HLR) over a Mapping of Address and Port with Encapsulation (MAP-E) interface to fetch registration status of end user. This integration is done via the STP 410.
[0075] The front end of the IPSMGW 402 integrates with the Element Management System (EMS) 412 over Representational State Transfer (REST) interface to share FCAPS (Fault, Configuration, Accounting, Performance, and Security) data of IPSMGW 402 application, IPSMGW 402 signaling front end and IPSMGW 402 antispam manager. The EMS 412 primarily supports fault management, performance management and configuration management of the nodes. EMS integrates with north bound OSS/BSS nodes i.e. Telecommunications Management Information Platform (TeMIP), My Communication (MyCOM), Hewlett-Packard Operations Orchestration (HPOO), Granite, Discovery and Reconciliation (DnR) for sharing FCAPs data.
[0076] FIG. 5 is a signal flow diagram for barring of the SMS according to one or more embodiments of the present invention.
[0077] At step 502, the IPSMGW 402 receives the SMS from the UE 102a.
[0078] At step 504, upon receiving the SMS from the UE 102a, the IPSMGW 402 determines the RAT type of the received SMS. To determine the RAT type of the received SMS, PANI header received along with the SMS is parsed to identify the RAT type.
[0079] At step 506, if the cell-ID is blocked in the PLMN, the IPSMGW 402 fetches the cell-ID information from the MT user (UE) 102b by transmitting the Type-0 message. In particular, the type 0 message is transmitted to retrieve the PANI header. The PANI header is subsequently parsed to identify the RAT type.
[0080] At step 508, upon identifying the RAT type, the IPSMGW 402 transmits the UDR message to one of the AMF and the MME via the HSS 420 to fetch the information pertaining to the location of the UE 102 from the HSS 420. The UDR message is transmitted to one of the AMF and the MME 425 via the HSS 420 to retrieve the information pertaining to the location of the UE 102a and the cell-ID of the UE 102a. The information pertaining to location of the UE 102a from the HSS 420 is retrieved when the RAT type is determined as the WLAN type.
[0081] At step 510, the HSS 420 responds to the IPSMGW 402 with the EPSLocationInformation in Sh data xml format and the cell-ID is encoded in Base64 Format. Further, the IPSMGW 402 decodes the format of the cell-ID and block accordingly.
[0082] At step 512, if the information pertaining to the location is not retrieved from the HSS 420 and a negative response is received from the HSS 420, the error code message is transmitted to the UE 102a or MT UE 102b. Further, upon retrieving the information pertaining to location of the UE 102a from the HSS 420, the retrieved information associated with the UE 102a is compared with the barred list. The retrieved information associated with the UE 102a with the barred list is compared to determine if the retrieved location is present in the barred list. The barred list includes one of, a location and a list of cell IDs within the location that are to be barred from transmitting SMS to other UEs 102a.
[0083] FIG. 6 is a flow diagram of a method 600 for barring of the SMS, according to one or more embodiments of the present invention. For the purpose of description, the method 600 is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
[0084] At step 602, the method 600 includes the step of receiving the SMS from the UE 102 by the receiving unit 210.
[0085] At step 604, the method 600 includes the step of determining the RAT type of the received SMS by the identifier unit 212. To determine the RAT type of the SMS, the method comprises the steps of one of parsing the PANI header received along with the SMS to identify the RAT type. In one embodiment, for the Mobile Terminated (MT) Short Message Service (SMS), when the cell-ID is blocked in a Public Land Mobile Network (PLMN), the IPSMGW 402 fetches the cell-ID information from a MT user by transmitting a Type-0 message. In particular, the identifier unit 212 is configured to transmit the type 0 message to retrieve the PANI header. The PANI header is subsequently parsed to identify the RAT type.
[0086] At step 606, the method 600 includes the step of retrieving information pertaining to location of the UE 102 from the HSS 420 when the RAT type is determined as the WLAN type by the retrieval unit 214. To retrieve the location information and the cell ID of the UE, the method comprises the step of transmitting the UDR message to one of, the AMF and the MME via the HSS 420 to retrieve the information pertaining to the location of the UE 102 and the cell ID of the UE 102. If one of the information pertaining to the location is not retrieved from the HSS 420 and a negative response is received from the HSS 420, the one or more processor is configured to transmit the error code to the UE 102.
[0087] At step 608, the method 600 includes the step of comparing the retrieved information associated with the UE 102 with a barred list to determine if the retrieved location is present in the barred list by the comparing unit 216. The step of comparing the retrieved information with the barred list comprises the steps of mapping the retrieved location of the UE 102 to the barred location in the barred list. In response to mapping of the location, mapping the cell ID of the UE 102 to the barred cell ID in the barred list.
[0088] At step 610, the method 600 includes the step of transmitting the error code in response to determination of presence of the location in the barred list by the transmittal unit 218. The barred list includes one of, a location and a list of cell IDs within the location that are to be barred from transmitting SMS to other UEs 102.
[0089] The present invention further discloses a non-transitory computer-readable medium having stored thereon computer-readable instructions. The computer-readable instructions are executed by the processor 202. The processor 202 is configured to receive the SMS from the UE 102. The processor 202 is further configured to determine the RAT type of the received SMS. The processor 202 is further configured to retrieve information pertaining to location of the UE from the HSS 420 when the RAT type is determined as WLAN type. The processor 202 is further configured to compare the retrieved information associated with the UE with the barred list to determine if the retrieved location is present in the barred list. The processor 202 is further configured to transmit the error code in response to determination of presence of the location in the barred list.
[0090] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.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.
[0091] The present disclosure incorporates technical advancement of determining the exact location of the UE even when connected to Wi-Fi so that if and when required location-based barring of services can be performed. The proposed solution guarantees comprehensive restrictions for all users using the UE, resulting in a 100 percent achievement of SMS barring. The present disclosure can be readily adopted into standard technology as it uses the standard interfaces, queries, and headers to fetch the location data of user using the UE.
[0092] 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

[0093] Environment- 100
[0094] User Equipment (UE)- 102, 102a, 102b
[0095] Server- 104
[0096] Network- 106
[0097] System -108
[0098] Processor- 202
[0099] Memory- 204
[00100] User Interface- 206
[00101] Database- 208
[00102] Interface Unit- 210
[00103] Identifier Unit- 212
[00104] Retrieval Unit- 214
[00105] Comparison Unit- 216
[00106] Transmittal Unit- 218
[00107] Primary processor- 302
[00108] Memory- 304
[00109] IPSMGW- 402
[00110] S-CSCF- 404
[00111] F5 Load balancer- 406a, 406b
[00112] DRA- 408
[00113] STP-410
[00114] EMS- 412
[00115] SMPP-CP- 414
[00116] MNP-416
[00117] OCS-418
[00118] HSS- 420
[00119] SCEF- 422
[00120] MME-424
,CLAIMS:CLAIMS:

We Claim:
1. A method (600) of barring of Short Message Service (SMS), the method (600) comprising the steps of:
receiving, by one or more processors (202), the SMS from a user equipment (UE) (102);
determining, by the one or more processors (202), a Radio Access Technology (RAT) type of the received SMS;
retrieving, by the one or more processors (202), information pertaining to location of the UE (102) from a Home Subscriber Server (HSS) (420) when the RAT type is determined as a Wireless Local Area Network (WLAN) type;
comparing, by the one or more processors (202), the retrieved information associated with the UE (102) with a barred list to determine if the retrieved location is present in the barred list; and
transmitting, by the one or more processors (202), an error code in response to determination of presence of the location in the barred list.

2. The method (600) as claimed in claim 1, wherein the step of comparing the retrieved information with the barred list comprises the steps of:
mapping, by the one or more processors (202), the retrieved location of the UE to a barred location in the barred list; and
in response to mapping of the location, mapping, by the one or more processors, a cell ID of the UE (102) to a barred cell ID in the barred list.

3. The method (600) as claimed in claim 1, wherein to determine the RAT type of the SMS, the method (600) comprises the steps of one of:
parsing, by the one or more processors (202), a P-Access-Network-Info (PANI) header received along with the SMS to identify the RAT type; and
transmitting, by the one or more processors (202), a type 0 message to retrieve a PANI header, the PANI header is subsequently parsed to identify the RAT type.

4. The method (600) as claimed in claim 1, wherein to retrieve the location information and the cell ID of the UE (102), the method comprises the step of:
transmitting, by the one or more processors (202), a User Data Request (UDR) message to one of, an Access and Mobility Management Function (AMF) and a Mobile Management Entity (MME) via the HSS (420) to retrieve the information pertaining to the location of the UE (102) and the cell ID of the UE (102).

5. The method (600) as claimed in claim 1, wherein if, one of, the information pertaining to the location is not retrieved from the HSS (420) and a negative response is received from the HSS (420), the one or more processor is configured to transmit the error code to the UE (102).

6. The method (600) as claimed in claim 1, wherein the barred list includes one of, a location and a list of cell IDs within the location that are to be barred from at least transmitting SMS to other UEs (102) or receiving SMS from other UEs (102).

7. A system (108) for barring of Short Message Service (SMS), the system (108) comprising:
an interface unit (210) configured to receive the SMS from a user equipment (UE) (102);
an identifier unit (212) configured to determine a Radio Access Technology (RAT) type of the received SMS;
a retrieval unit (214) configured to retrieve information pertaining to location of the UE (102) from a Home Subscriber Server (HSS) (420) when the RAT type is determined as a Wireless Local Area Network (WLAN) type;
a comparison unit (216) configured to compare the retrieved information associated with the UE (102) with a barred list to determine if the retrieved location is present in the barred list; and
a transmittal unit (218) configured to transmit an error code in response to determination of presence of the location in the barred list.

8. The system (108) as claimed in claim 7, wherein the comparison unit (216) is configured to:
map the retrieved location of the UE (102) to a barred location in the barred list; and
in response to mapping of the location, map, a cell ID of the UE (102) to a barred cell ID in the barred list.

9. The system (108) as claimed in claim 7, wherein the identifier unit (212) is further configured to one of:
parse a P-Access-Network-Info (PANI) header received along with the SMS to identify the RAT type; and
transmit a type 0 message to retrieve a PANI header, the PANI header is subsequently parsed to identify the RAT type.

10. The system (108) as claimed in claim 7, wherein the retrieval unit (214) is further configured to transmit a User Data Request (UDR) message to one of an Access and Mobility Management Function (AMF) and a Mobile Management Entity (MME) via the HSS (420) to retrieve the information pertaining to the location of the UE (102) and the cell ID of the UE (102).

11. The system (108) as claimed in claim 7, wherein if, one of, the information pertaining to the location is not retrieved from the HSS (420) and a negative response is received from the HSS (420), the retrieval unit is configured to transmit the error code to the UE (102).

12. The system (108) as claimed in claim 7, wherein the barred list includes one of, a location and a list of cell IDs within the location that are to be barred from at least transmitting SMS to other UEs (102) or receiving SMS from other UEs (102).

13. A User Equipment (UE) (102), comprising:
one or more primary processors (302) communicatively coupled to one or more processors (202), the one or more primary processors (302) coupled with a memory (404), wherein said memory (304) stores instructions which when executed by the one or more primary processors (302) causes the UE (102) to:
transmit, a short message service (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.