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 MANAGING COMMUNICATION BETWEEN USER EQUIPMENTS
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 the field of communication systems, and more particularly relates to a method and system managing communication between User Equipments (UEs).
BACKGROUND OF THE INVENTION
[0002] Internet of Things (IoT) is a revolutionary concept that enables devices and machines to communicate with each other over networks using automated applications. These devices, often equipped with sensors and actuators, can collect and exchange data, enabling various applications and services. IoT has found applications in diverse domains such as healthcare, transportation, agriculture, and smart homes, among others.
[0003] In order to control and manage IoT devices, various methods are employed, including SMS (Short Message Service) or other inputs. These devices can be assigned unique identifiers, such as Mobile Station Integrated Services Digital Network (MSISDN) numbers, which are typically associated with telecommunication networks. MSISDN is a globally unique number that identifies a subscription in a mobile network. In the context of IoT, MSISDN numbers serve as identifiers for IoT devices, allowing them to connect to the network, send and receive messages, and interact with other devices or applications.
[0004] However, a significant problem arises when users, unaware of the purpose of MSISDN numbers associated with IoT devices, send messages to these numbers without considering their intended use. For example, a user might mistakenly send a regular text message or initiate a voice call to an IoT device's MSISDN. Since IoT devices are not designed to handle such communication, these messages may cause malfunctions, disrupt device operations, or lead to undesirable consequences.
[0005] There is a need to address the aforementioned issues by providing a solution for securing IoT devices from unauthorized access and potential disruptions caused by external communication. There is a need for a solution, by which, the IoT 3 devices can be protected from unintended interactions, ensuring their proper functioning and mitigating potential disruptions caused by external messages.
[0006] For example, consider a scenario where an IoT device is deployed in a critical infrastructure system, such as a power plant. The IoT device is assigned a unique MSISDN for communication purposes. However, other users who are not aware of the device's intended use or the associated MSISDN may send regular text messages or initiate voice calls to the device's number. These unintended interactions can cause the device to malfunction or generate false alarms, potentially jeopardizing the entire power plant's operations and safety.
[0007] To prevent such incidents, the present invention provides a mechanism for whitelisting allowed numbers to the IoT device's MSISDN. Only authorized users or specific applications listed in the whitelist are permitted to send or receive messages from the IoT device. This ensures that only intended communications reach the device, minimizing the risk of malfunctions, disruptions, or compromised security.
[0008] In view of the foregoing, there is a need for an improved method and system that enables the whitelisting of allowed numbers to a wide band (WB) IoT number, providing enhanced security and ensuring the smooth operation of IoT devices.
SUMMARY OF THE INVENTION
[0009] One or more embodiments of the present disclosure provide a method and a system for managing communication between User Equipments (UEs).
[0010] In one aspect of the present invention, the system for managing communication between the UEs is disclosed. The system includes a receiving unit configured to receive a message from a first user equipment (UE) or a second UE to initiate communication between the first UE and the second UE. The message includes a numerical identifier corresponding to the first UE or the second UE. The system further includes a determination unit configured to determine if the first UE is associated to a Machine to Machine (M2M) user. The system further includes a transmitting unit configured to transmit a User Data Request (UDR) to a Home Subscriber Server (HSS) over a communication interface upon determining the first UE is associated to the M2M user. The system further includes a retrieving unit configured to retrieve a user profile corresponding to the first UE or the second UE from the HSS in response to transmitting the UDR to the HSS. The system further includes a parsing unit configured to parse the user profile to determine if a numerical identifier corresponding to the first UE or the second UE is available or unavailable in the user profile. The system further includes a managing unit configured to manage the communication between the first UE and the second UE in response to determining if the numerical identifier corresponding to the first UE or the second UE is available or unavailable in the user profile.
[0011] In an embodiment, the message is one of a Session Initiation Protocol (SIP) message to initiate the communication between the first UE and the second UE.
[0012] In an embodiment, the UDR includes a Mobile Subscriber Integrated Services Digital Network (MSISDN) of the first UE as a username.
[0013] In an embodiment, the user profile indicates a list of numerical identifiers corresponding to one or more of the UEs, which is allowed to or restricted from communicating with the first UE or the second UE.
[0014] In an embodiment, the managing unit is configured to allow the communication between the first UE and the second UE if the numerical identifier corresponding to the first UE or the second UE is available in the user profile.
[0015] In one embodiment, the managing unit is configured to bar the communication between the first UE and the second UE if the numerical identifier corresponding to the first UE or the second UE is unavailable in the user profile.
[0016] In another aspect of the present invention, the method of managing communication between UEs is disclosed. The method further includes the step of receiving a message from a first user equipment (UE) or a second UE to initiate communication between the first UE and a second UE. The message includes a numerical identifier corresponding to the first UE or the second UE. The method further includes the step of determining if the first UE is associated to a Machine to Machine (M2M) user. The method further includes the step of transmitting a User Data Request (UDR) to a Home Subscriber Server (HSS) over a communication interface upon determining the first UE is associated to the M2M user. The method further includes the step of retrieving a user profile corresponding to the first UE or the second UE from the HSS in response to transmitting the UDR to the HSS. The method further includes the step of parsing the user profile to determine if a numerical identifier corresponding to the first UE or the second UE is available or unavailable in the user profile. The method further includes the step of managing the communication between the first and the second UE in response to determining if the numerical identifier corresponding to the first UE or the second UE is available or unavailable in the user profile.
[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 a message from a first user equipment (UE) or a second UE to initiate communication between the first UE and a second UE. The message includes a numerical identifier corresponding to the first UE or the second UE. The processor is further configured to determine if the first UE is associated to a Machine to Machine (M2M) user. The processor is further configured to transmit a User Data Request (UDR) to a Home Subscriber Server (HSS) over a communication interface upon determining the first UE is associated to the M2M user. The processor is further configured to retrieve a user profile corresponding to the first UE or the second UE from the HSS in response to transmitting the UDR to the HSS. The processor is further configured to parse the user profile to determine if a numerical identifier corresponding to the first UE or the second UE is available or unavailable in the user profile. The processor is further configured to manage the communication between the first and the second UE in response to determining if the numerical identifier corresponding to the first UE or the second UE is available or unavailable in the user profile.
[0018] In another aspect of invention, User Equipments (UEs) is disclosed. The UEs include one or more primary processors communicatively coupled to one or more processors, the one or more primary processors coupled with a memory. The processor causes the UEs to transmit a message to initiate communication between the first UE and a second UE. The message includes a numerical identifier corresponding to the first UE or the second UE.
[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 managing communication between User Equipments (UEs), according to one or more embodiments of the present invention;
[0022] FIG. 2 an exemplary block diagram of a system for managing communication between UEs, 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 an exemplary signal flow diagram for managing communication between UEs, according to one or more embodiments of the present invention; and
[0026] FIG. 6 is a schematic representation of a method for managing communication between UEs, 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 method and system of the present invention provides the functionality of the IP Short Message Gateway (IPSMGW) node, which acts as the decision-making point for Short Message Service (SMS) services in the IP Multimedia Subsystem (IMS) network. When a message is received, the IPSMGW verifies the sender's number with the downloaded list from the Home Subscriber Service (HSS). If the number is not present in the allowed numbers list, the IPSMGW restricts the message by sending a RP-ERROR response with an operator-determined barring reason.
[0032] FIG. 1 illustrates an exemplary block diagram of an environment 100 for managing communication between User Equipments (UEs), according to one or more embodiments of the present disclosure. As per the illustrated embodiment, the UEs is one of a first UE 102 and a second UE 112, without limiting the scope of the present disclosure. In alternate embodiments, the UEs may include multiple number of UEs as per requirement. In this regard, the environment 100 includes the first UE 102, a server 104, a network 106, the second UE 112 and a system 108 communicably coupled to each other for managing communication between the UEs. The first UE 102 aids a user to interact with the system 108 for transmitting a message to initiate communication between the first UE 102 and the second UE 112.
[0033] In an embodiment, each of the first UE 102 is one of Internet of Things (IOT) devices. The IOT devices include, but not limited to, cellular based IOT devices: NB-IoT & WB-IoT, UAVs, aerial robotics, connected cars and V2X and so forth.
[0034] In an embodiment, the second UE 112 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] In one embodiment, the first UE 102 can be the IOT device, and the second UE 112 is a normal UE such as, but not limited to a cell phone. In such case, the SMS sent by the second UE 112 to the first UE 102 is one of, but not limited to, wake, authenticate, request, perform IOT process/operation, command.
[0036] 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.
[0037] 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.
[0038] 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.
[0039] The environment 100 further includes the system 108 communicably coupled to the server 104 and the first UE 102 and the second UE 112. The system 108 is configured for managing communication between UEs. As per one or more embodiments, the system 108 is adapted to be embedded within the server 104 or embedded as an individual entity.
[0040] Operational and construction features of the system 108 will be explained in detail with respect to the following figures.
[0041] FIG. 2 is an exemplary block diagram of the system 108 for managing communications between the UEs, according to one or more embodiments of the present invention. More specifically, the FIG. 2 is the exemplary block diagram of the system 108 for managing communication between the first UE 102 (as shown in FIG. 1) and the second UE 112 (as shown in FIG. 1).
[0042] 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 (as shown in FIG. 1). 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.
[0043] 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.
[0044] 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 first UE 102, the second UE 112, and the database 208.
[0045] 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.
[0046] In order for the system 108 to manage communication between UEs, the processor 202 includes one or more modules. In one embodiment, the one or more modules includes, but not limited to, a receiving unit 210, a determination unit 212, a transmitting unit 214, a retrieving unit 216, a parsing unit 218 and a managing unit 220 communicably coupled to each other for managing communication between the first UE 102 and the second UE 112. Further, the processor 202 is communicably coupled with a Home Subscriber Server (HSS) 224 for managing communication between UEs.
[0047] The receiving unit 210, the determination unit 212, the transmitting unit 214, the retrieving unit 216, the parsing unit 218, the managing unit 220, and the HSS 224 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.
[0048] In one embodiment, in order to manage the communication between the UEs a message is received from the first UE 102. The message is received from the first UE 102 by the receiving unit 210 to initiate communication between the first UE 102 and the second UE 112. The message includes a numerical identifier corresponding to the first UE 102. The numerical identifier is a unique number or code assigned to the first UE 102 and the second UE 112 in the network 106. The numerical identifiers include, but not limited to, an International Mobile Subscriber Identity (IMSI), an International Mobile Equipment Identity (IMEI), a Temporary Mobile Subscriber Identity (TMSI), a Mobile Station International Subscriber Directory Number (MSISDN), and a Global Unique Temporary Identifier (GUTI). In one embodiment, the message is at least one of, but not limited to, a Session Initiation Protocol (SIP) message to initiate communication between the first UE 102 and the second UE 112. The SIP is a signaling protocol used for initiating, maintaining, and terminating communication sessions that include voice, video and messaging applications.
[0049] Upon receiving the message from the first UE 102 by the receiving unit 210, the determination unit 212 is configured to determine if the first UE 102 is associated to a Machine to Machine (M2M) user. The M2M users refers to the first UE 102 and the second UE 112 that communicate with each other without human intervention. The M2M user has a 13-digit number series based on that IP Short Message Gateway (IP-SM-GW) identifies the M2M user.
[0050] Upon determining the first UE 102 is associated to the M2M user, the transmitting unit 214 is configured to transmit the UDR to the HSS 224 over a communication interface. The UDR includes a Mobile Subscriber Integrated Services Digital Network (MSISDN) of the first UE as a username. 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]
[0051] The HSS 224 stores subscriber-related information and plays a role in the authentication, authorization, and management of subscribers. The key functions of the HSS 224 include, but are not limited to, subscriber data management, authentication and authorization, mobility management, subscriber management and interoperability. The communication interface is defined as a standardized point of interaction between different network elements that facilitates the exchange of data, signaling, and control messages. The communication interface includes, but not limited to, S1 interface, S6a interface, X2 interface, Gi interface, Gx interface, Cx/Dx interface.
[0052] In response to transmitting the UDR to the HSS 224, the retrieving unit 216 is configured to retrieve a user profile corresponding to the first UE 102 from the HSS 224. In an embodiment, the list of user profile is checked in User Data Answer (UDA). 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]
[0053] The user profile indicates a list of numerical identifiers corresponding to one or more of the UEs, which is allowed to or restricted from communicating with the first UE 102. The numerical identifiers are essential for managing and distinguishing different UEs and their services within the network 106. The list of numerical identifiers includes, but not limited to International Mobile Subscriber Identity (IMSI), the MSISDN, International Mobile Equipment Identity (IMEI), Temporary Mobile Subscriber Identity (TMSI), Globally Unique Temporary Identifier (GUTI), Subscription Permanent Identifier (SUPI), International Mobile Equipment Identity and Software Version (IMEISV), Public Land Mobile Network Identifier (PLMN ID), Universal Temporary Mobile Subscriber Identity (U-TMSI). The user profile also includes UE capability. The UE capability indicates whether the UE (such as IOT) has the capability to send/receive SMS. The capability can be related to at least one of, but not limited to, billing reasons, SMS support, incompatibility.
[0054] Thereafter, the user profile is parsed by the parsing unit 218, to determine if a numerical identifier corresponding to the second UE 112 is available or unavailable in the user profile. In response to determining if the numerical identifier corresponding to the second UE 112 is available or unavailable in the user profile, the managing unit 220 is configured to manage the communication between the first UE 102 and the second UE 112.
[0055] If the numerical identifier corresponding to the second UE 112 is available in the user profile, the managing unit 220 is configured to allow the communication between the first UE 102 and the second UE 112. Alternatively, if the numerical identifier corresponding to the second UE 112 is unavailable in the user profile, the managing unit 220 is configured to bar the communication between the first UE 102 and the second UE 112. In one embodiment, the system 108 restricts the message by transmitting a RP-ERROR response to the first UE 102 with an operator-determined barring reason if the numerical identifier corresponding to the second UE 112 is unavailable. The RP-ERROR message is sent between a Mobile Switching Center (MSC) and a mobile station in both directions and used to relay an error caused from an erroneous short message or notification transfer attempt. Therefore, the system 108 secures the UEs by restricting communication to allowed numbers, preventing malfunctions, and minimizing the potential risks posed by unauthorized access.
[0056] In one embodiment, in order to manage the communication between the UEs, the message is received from the second UE 112. The message is received from the second UE 112 by the receiving unit 210 to initiate communication between the first UE 102 and the second UE 112. The message includes the numerical identifier corresponding to the second UE 112. In one embodiment, the message is at least one of, but not limited to, the SIP message to initiate communication between the first UE 102 and the second UE 112.
[0057] Upon receiving the message from the second UE 112 by the receiving unit 210, the determination unit 212 is configured to determine if the first UE 102 is associated to the M2M user.
[0058] Upon determining that the first UE 102 is associated to the M2M user, the transmitting unit 214 is configured to transmit the UDR to the HSS 224 over the communication interface. The UDR includes the MSISDN of the first UE as the username.
[0059] In response to transmitting the UDR to the HSS 224, the retrieving unit 216 is configured to retrieve the user profile corresponding to the second UE 112 from the HSS 224. In an embodiment, the list of user profile is checked in User Data Answer (UDA). The UDA is sent by the server 104 in response to the User-Data-Request command. The user profile indicates the list of numerical identifiers corresponding to one or more of the UEs, which is allowed to or restricted from communicating with the second UE 112.
[0060] Thereafter, the user profile is parsed by the parsing unit 218, to determine if the numerical identifier corresponding to the first UE 102 is available or unavailable in the user profile. In response to determining if the numerical identifier corresponding to the first UE 102 is available or unavailable in the user profile, the managing unit 220 is configured to manage the communication between the first UE 102 and the second UE 112.
[0061] If the numerical identifier corresponding to the first UE 102 is available in the user profile, the managing unit 220 is configured to allow the communication between the first UE 102 and the second UE 112. Alternatively, if the numerical identifier corresponding to the first UE 102 is unavailable in the user profile, the managing unit 220 is configured to bar the communication between the first UE 102 and the second UE 112. Therefore, the system 108 secures the UEs by restricting communication to allowed numbers, preventing malfunctions, and minimizing the potential risks posed by unauthorized access.
[0062] 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 both the UEs 102, 112 (first UE 102, second UE 112) 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.
[0063] As mentioned earlier in FIG. 1, the first UE 102 or the second UE 112 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 102 or the second UE 112 without deviating from the scope of the present disclosure and the limiting the scope of the present disclosure. The first UE 102 or the second UE 112 includes one or more primary processors 302 communicably coupled to the one or more processors 202 of the system 108.
[0064] The one or more primary processors 302 are coupled with a memory 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 102 or the second UE 112 to transmit the message to initiate communication between the first UE 102 and the second UE 112. The message includes the numerical identifier corresponding to the first UE 102 or the second UE 112.
[0065] As mentioned earlier in FIG. 2, the one or more processors 202 of the system 108 is configured for managing communication between UEs 102, 112. 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.
[0066] Further, the processor 202 includes the receiving unit 210, the determination unit 212, the transmitting unit 214, the retrieving unit 216, the parsing unit 218, the managing unit 220. Further, the HSS 224 is communicably coupled with the processor 202. The operations and functions of the receiving unit 210, the determination unit 212, the transmitting unit 214, the retrieving unit 216, the parsing unit 218, the managing unit 220, and the HSS 224 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.
[0067] FIG. 4 is an exemplary block diagram of an architecture 400 of the system 108 of the FIG. 2, according to one or more embodiments of the present invention.
[0068] 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.
[0069] The IPSMGW 402 integrates with the S-CSCF 404 over the ISC (IP Service Control) interface. The integration between the IPSMGW 402 and the S-CSCF 404 enables the IPSMGW 402 to handle third-party registrations and forward Short Message Service (SMS) messages originated from the first UE 102 towards the IPSMGW 402.
[0070] In addition, the IPSMGW 402 integrates with the Mobile Number Portability (MNP) 416 over the Session Initiation Protocol (SIP) interface. The integration between the IPSMGW 402 and the MNP 416 allows the IPSMGW 402 to perform MNP 416 queries to obtain Routable Numbers (RN) and outbound mobile numbers for message routing. In one embodiment, the F5 load balancer 406a and 406b is configured for routing the queries.
[0071] The IPSMGW 402 also connects with the Online Charging System (OCS) 418 over the RO (Request-Answer) interface based on the diameter protocol. The integration between the IPSMGW 402 and the OCS 418 facilitates IP Multimedia Subsystem (IMS) online charging for both pre-paid and post-paid subscribers. Further, the IPSMGW 402 communicates with the HSS 224 over the Sh interface to retrieve user registration data.
[0072] The IPSMGW 402 integrates with Short Message Peer-to-Peer (SMPP) Content Providers (CP) 414 over the SMPP interface, enabling P2A (Person-to-Application) or A2P (Application-to-Person) SMS services. The A2P IPSMGW connects with the P2P IPSMGW over the SMPP interface. The integration facilitates the transfer of SMPP requests from the first UE 102 to the A2P IPSMGW.
[0073] The IPSMGW 402 also connects with the Service Capability Exposure Function (SCEF) 422 over the T4 (Application Layer Traffic Optimization) interface based on the diameter protocol. The integration between the IPSMGW 402 and the SCEF 422 allows the IPSMGW 402 to receive device trigger messages.
[0074] In addition, the IPSMGW 402 connects with a Mobility Management Entity (MME) 424 over the SGd (Diameter Routing) interface. The integration between the IPSMGW 402 and the MME 424 enable the IPSMGW 402 to fetch the terminating IPSMGW 402 address and terminate device trigger messages for users.
[0075] In one embodiment, the IPSMGW 402 Signalling Frontend component integrates with the STP 410 over the Mobile Application Part-Enhanced (MAP) interface. The integration between the IPSMGW 402 and the STP 410 allows the IPSMGW 402 Signalling Frontend to fetch the registration status of end users.
[0076] The IPSMGW 402 Signalling Frontend also integrates with the EMS 412 over the Representational State Transfer (REST) interface. The integration between the IPSMGW 402 and the EMS 412 facilitates the sharing of FCAPS (Fault, Configuration, Accounting, Performance, and Security) data between the IPSMGW Signalling Frontend, IPSMGW Application, and IPSMGW Antispam Manager. The sharing supports fault management, performance management, and configuration management of these nodes. The EMS 412 component integrates with various northbound Operations Support System/Business Support System (OSS/BSS) nodes, such as TeMIP, MyCOM, HPOO, Granite, and DnR. These integrations enable the sharing of FCAPS data with the operations team for effective management of the IPSMGW 402 system. In one embodiment, the database 208 is provided to store data.
[0077] FIG. 5 is an exemplary signal flow diagram for managing communications between the UEs, according to one or more embodiments of the present invention
[0078] At step 502, the first UE 102 or the second UE 112 transmits the message to the IPSMGW 402. The message received from the first UE 102 or the second UE 112 to initiate communication between the first UE 102 and the second UE 112. The message includes the numerical identifier corresponding to the first UE 102 or the second UE 112. The message is one of the SIP message to initiate the communication between the first UE 102 and the second UE 112. Upon receiving the message from the first UE 102 or the second UE 112, the IPSMGW 402 determines if the first UE 102 is associated to the M2M user.
[0079] At step 504, upon determining the first UE 102 is associated to the M2M user, the UDR is transmitted to the HSS 224 over the communication interface. The UDR includes the MSISDN of the first UE 102 as the username.
[0080] At step 506, in response to transmitting the UDR to the HSS 224, the user profile corresponding to the first UE 102 or the second UE 112 is retrieved from the HSS 224. The user profile indicates the list of numerical identifiers corresponding to one or more of the UEs, which is allowed to or restricted from communicating with the first UE 102 or the second UE 112.
[0081] At step 508, upon retrieving the user profile, the user profile is parsed to determine if a numerical identifier corresponding to the first UE 102 or the second UE 112 is available or unavailable in the user profile.
[0082] At step 510, in response to parsing the user profile, the communication between the first UE 102 and the second UE 112 is managed. The communication between the first UE 102 and the second UE 112 is managed based on determining if the numerical identifier corresponding to the first UE 102 or the second UE 112 is available or unavailable in the user profile. If the numerical identifier corresponding to the first UE 102 or the second UE 112 is available in the user profile, the communication between the first UE 102 and the second UE 112 is allowed. Alternatively, if the numerical identifier corresponding to the first UE 102 or the second UE 112 is unavailable in the user profile, the communication between the first UE 102 and the second UE 112 is barred.
[0083] At step 512, if the numerical identifier corresponding to the second UE 112 is unavailable, a RP-ERROR response is transmitted to the first UE 102.
[0084] FIG. 6 is a flow diagram of a method 600 for managing communications between UEs, 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.
[0085] At step 602, the method 600 includes the step of receiving the message from the first UE 102 or the second UE 112 to initiate communication between the first UE 102 and the second UE 112 by the receiving unit 210. The message includes the numerical identifier corresponding to the first UE 102 or the second UE 112.
[0086] At step 604, the method 600 includes the step of determining if the first UE 102 is associated to the M2M user by the determination unit 212.
[0087] At step 606, the method 600 includes the step of transmitting the UDR to the HSS 224 over the communication interface by the transmitting unit 214. The UDR includes the MSISDN of the first UE 102 as the username.
[0088] At step 608, the method 600 includes the step of retrieving the user profile corresponding to the first UE 102 or the second UE 112 from the HSS 224 by the retrieving unit 216. The user profile indicates the list of numerical identifiers corresponding to one or more of the UEs, which is allowed to or restricted from communicating with the first UE 102 or the second UE 112.
[0089] At step 610, the method 600 includes the step of parsing the user profile to determine if the numerical identifier corresponding to the first UE 102 or the second UE 112 is available or unavailable in the user profile by the parsing unit 218.
[0090] At step 612, the method 600 includes the step of managing the communication between the first UE 102 and the second UE 112 by the managing unit 220 in response to determining if the numerical identifier corresponding to the first UE 102 or the second UE 112 is available or unavailable in the user profile. The method 600 includes the step of allowing the communication between the first UE 102 and the second UE 112 if the numerical identifier corresponding to the first UE 102 or the second UE 112 is available in the user profile. The method 600 further includes the step of barring communication between the first UE 102 and the second UE 112 if the numerical identifier corresponding to the first UE 102 or the second UE 112 is unavailable in the user profile.
[0091] 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 message from the first UE 102 or the second UE 112 to initiate communication between the first UE 102 and the second UE 112. The processor 202 is further configured to determine if the first UE 102 is associated to the M2M user. The processor 202 is further configured to transmit the UDR to the HSS 224 over the communication interface upon determining the first UE 102 is associated to the M2M user. The processor 202 is further configured to retrieve the user profile corresponding to the first UE 102 or the second UE 112 from the HSS 224 in response to transmitting the UDR to the HSS 224. The processor 202 is further configured to parse the user profile to determine if the numerical identifier corresponding to the first UE 102 or the second UE 112 is available or unavailable in the user profile. The processor 202 is further configured to manage the communication between the first UE 102 and the second UE 112 in response to determining if the numerical identifier corresponding to the first UE 102 or the second UE 112 is available or unavailable in the user profile.
[0092] 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.
[0093] The present disclosure incorporates technical advancement of enhancing the security and integrity of UEs and ensuring proper functioning of UE and mitigating the risk of disruptions caused by unauthorized communication. In particular, the UE is secured by restricting communication to allowed numbers, preventing malfunctions, and minimizing the potential risks posed by unauthorized access.
[0094] 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

[0095] Environment- 100
[0096] First User Equipment (UE)- 102
[0097] Second User Equipment (UE)- 112
[0098] Server- 104
[0099] Network- 106
[00100] System -108
[00101] Processor- 202
[00102] Memory- 204
[00103] User Interface- 206
[00104] Database- 208
[00105] Receiving Unit- 210
[00106] Determination Unit- 212
[00107] Transmitting Unit- 214
[00108] Retrieving Unit- 216
[00109] Parsing Unit- 218
[00110] Managing Unit- 220
[00111] HSS- 224
[00112] Primary processor- 302
[00113] Memory- 304
[00114] IPSMGW- 402
[00115] S-CSCF- 404
[00116] F5 Load balancer- 406a, 406b
[00117] DRA- 408
[00118] STP-410
[00119] EMS- 412
[00120] SMPP-CP- 414
[00121] MNP-416
[00122] OCS-418
[00123] SCEF- 422
[00124] MME-424

,CLAIMS:CLAIMS:

We Claim:
1. A method (600) of managing communication between User Equipments (UEs) (102, 112), the method (600) comprising the steps of:
receiving, by one or more processors (202), a message from a first user equipment (UE) (102) or a second UE (112) to initiate communication between the first UE (102) and the second UE (112), wherein the message includes a numerical identifier corresponding to the first UE (102) or the second UE (112);
determining, by the one or more processors (202), if the first UE is associated to a Machine to Machine (M2M) user;
transmitting, by the one or more processors (202), a User Data Request (UDR) to a Home Subscriber Server (HSS) (224) over a communication interface upon determining the first UE (102) is associated to the M2M user;
retrieving, by the one or more processors (202), a user profile corresponding to the first UE (102) or the second UE (112) from the HSS (224) in response to transmitting the UDR to the HSS (224);
parsing, by the one or more processors (202), the user profile to determine if a numerical identifier corresponding to the first UE (102) or the second UE (112) is available or unavailable in the user profile; and
managing, by the one or more processors (202), the communication between the first UE (102) and the second UE (112) in response to determining if the numerical identifier corresponding to the first UE (102) or the second UE (112) is available or unavailable in the user profile.

2. The method (600) as claimed in claim 1, wherein the message is one of a Session Initiation Protocol (SIP) message to initiate the communication between the first UE (102) and the second UE (112).

3. The method (600) as claimed in claim 1, wherein the UDR includes a Mobile Subscriber Integrated Services Digital Network (MSISDN) of the first UE (102) as a username.

4. The method (600) as claimed in claim 1, wherein the user profile indicates a list of numerical identifiers corresponding to one or more of the UEs, which is allowed to or restricted from communicating with the first UE (102) or the second UE (112).

5. The method (600) as claimed in claim 1, wherein the method (600) includes the step of allowing, by the one or more processors (202), the communication between the first UE (102) and the second UE (112) if the numerical identifier corresponding to the first UE (102) or the second UE (112) is available in the user profile.

6. The method (600) as claimed in claim 1, wherein the method (600) includes the step of barring, by the one or more processors (202), communication between the first UE (102) and the second UE (112) if the numerical identifier corresponding to the first UE (102) or the second UE (112) is unavailable in the user profile.

7. A system (108) for managing communication between user equipments (UEs) (102, 112), the system (108) comprising:
a receiving unit (210) configured to receive, a message from a first user equipment (UE) (102) or a second UE (112) to initiate communication between the first UE (102) and a second UE (112), wherein the message includes a numerical identifier corresponding to the first UE (102) or the second UE (112);
a determination unit (212) configured to determine, if the first UE (102) is associated to a Machine to Machine (M2M) user;
a transmitting unit (214) configured to transmit, a User Data Request (UDR) to a Home Subscriber Server (HSS) (224) over a communication interface upon determining the first UE (102) is associated to the M2M user;
a retrieving unit (216) configured to retrieve, a user profile corresponding to the first UE (102) or the second UE (112) from the HSS (224) in response to transmitting the UDR to the HSS (224);
a parsing unit (218) configured to parse, the user profile to determine if a numerical identifier corresponding to the first UE (102) or the second UE (112) is available or unavailable in the user profile; and
a managing unit configured to manage, the communication between the first UE (102) and the second UE (112) in response to determining if the numerical identifier corresponding to the first UE (102) or the second UE (112) is available or unavailable in the user profile.

8. The system (108) as claimed in claim 7, wherein the message is one of a Session Initiation Protocol (SIP) message to initiate the communication between the first UE (102) and the second UE (112).

9. The system (108) as claimed in claim 7, wherein the UDR includes a Mobile Subscriber Integrated Services Digital Network (MSISDN) of the first UE (102) as a username.

10. The system (108) as claimed in claim 7, wherein the user profile indicates a list of numerical identifiers corresponding to one or more of the UEs, which is allowed to or restricted from communicating with the first UE (102) or the second UE (112).

11. The system (108) as claimed in claim 7, wherein the managing unit (220) is configured to allow, the communication between the first UE (102) and the second UE (112) if the numerical identifier corresponding to the first UE (102) or the second UE (112) is available in the user profile.

12. The system (108) as claimed in claim 7, wherein the managing unit is configured to bar, the communication between the first UE (102) and the second UE (112) if the numerical identifier corresponding to the first UE (102) or the second UE (112) is unavailable in the user profile.

13. User Equipments (UEs) including a first UE (102) and a second UE (112), each of first UE (102) and the second UE (112) 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 (304), wherein said memory (304) stores instructions which when executed by the one or more primary processors (302) causes the UEs (102, 112) to:
transmit, a message to initiate communication between the first UE (102) and the second UE (112), wherein the message includes a numerical identifier corresponding to the first UE (102) or the second UE (112); and
wherein the one or more processors (202) is configured to perform the steps as claimed in claim 1.