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
SYSTEM AND METHOD FOR MANAGING A SUBSCRIBER IDENTITY MODULE (SIM) SWAP INFORMATION

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 wireless communication systems, more particularly relates to a method and system for managing a Subscriber Identity Module (SIM) swap information.
BACKGROUND OF THE INVENTION
[0002] In general, Subscriber Identity Module (SIM) swaps are a fraud in which a fraudster takes over a user's account by fraudulently managing to obtain a user’s phone number transferred to the fraudster’s SIM card and ultimately, his/her smartphone.
[0003] Once the SIM card is activated on the fraudster's device, all financial SMS of a user is vulnerable to SIM swap attacks. Fraudsters can take advantage of multi-factor authentication methods to take over the user’s accounts. By using a password reset function, the fraudster can get one-time passwords delivered via the Short Messaging Service (SMS) sent to the fraudster’s mobile device. Hence, SIM Swapping makes the one-time passwords (OTP) extremely vulnerable to attacks.
[0004] Therefore, there is a need to check the SIM swap of the user and to manage a Subscriber Identity Module (SIM) swap information by retrieving the SIM swap information. In one scenario, checking the retrieved SIM swap information for the multiple users along with the historical data of the SIM swap information is time consuming and a cumbersome task. Therefore, there is a need for to manage the SIM swap information in order to make the process of managing SIM swap information feasible for checking.
SUMMARY OF THE INVENTION
[0005] One or more embodiments of the present disclosure provide a method and system for managing a Subscriber Identity Module (SIM) swap information.
[0006] In one aspect of the present invention, a method for managing a Subscriber Identity Module (SIM) swap information is disclosed. The method includes the step of receiving a request pertaining to the SIM swap for a time interval, the request received from an entity via an entity gateway, wherein the time interval is defined by the entity. The method further includes the step of determining if the SIM swap information for the time interval as defined in the received request is stored in a storage unit. The method further includes the step of retrieving the SIM swap information for the time interval from the storage unit in response to determining the SIM swap information being stored in the storage unit.
[0007] In one embodiment, on retrieving the SIM swap information for the time interval from the storage unit, the one or more processors is further configured to perform the step of transmitting the retrieved SIM swap information related the time interval to the entity via the entity gateway.
[0008] In another embodiment, the entity is at least one of a third-party application function entity, an application, a developer, and an enterprise.
[0009] In yet another embodiment, the request pertaining to the SIM swap is received subsequent to authentication of the entity with respect to the entity gateway.
[0010] In yet another embodiment, upon authentication of the entity, the entity is configured to transmit a SIM swap to the one or more processors via a communication protocol.
[0011] In yet another embodiment, based on the SIM swap request, the one or more processors is configured to one of, retrieve timestamp and location of the timestamp of SIM swap performed for the SIM registered to a network provider.
[0012] In yet another embodiment, the step of determining, by the one or more processors, if the SIM swap information for the time interval as defined in the received request is stored in a storage unit by receiving at a first network element, an attachment information pertaining to a user equipment including the SIM, the attachment information is for one of a first-time attachment and for re-attachment. Further receiving at a second network element the attachment information from the first network element. Thereafter, transmitting by the second network element a request to transmit the attachment information to the one or more processor. Further, comparing by the one or more processors, the attachment information related to the first-time attachment and the re-attachment to determine if the attachment information and re-attachment is one of identical and different. Further storing by the one or more processors the SIM swap information in response to the attachment information being different to the re-attachment information.
[0013] In yet another embodiment, the attachment information related to the first-time attachment includes International Mobile Equipment Identity (IMEI), International Mobile Subscriber Identity (IMSI), Mobile Station International Subscriber Directory Number (MSISDN).
[0014] In yet another embodiment, the attachment information related to the re-attachment includes timestamp of the latest SIM swap status, change in International Mobile Subscriber Identity (IMSI), change in International Mobile Equipment Identity (IMEI), timestamp of last Mobile Station International Subscriber Directory Number (MSISDN) retrieved.
[0015] In yet another embodiment, wherein the attachment information related to the first-time attachment and the re-attachment is different if one of, International Mobile Equipment Identity (IMEI), International Mobile Subscriber Identity (IMSI) and Mobile Station International Subscriber Directory Number (MSISDN) of the Subscriber Identity Module (SIM) related to the re-attachment is different from the IMEI, IMSI, and MSISDN related to the first-time attachment after the SIM swap.
[0016] In another aspect of the present invention, a system for managing a Subscriber Identity Module (SIM) swap information is disclosed. The system includes a receiving unit configured to receive a request pertaining to check the SIM swap for a time interval, the request received from an entity via an entity gateway, the time interval is defined by the entity. The system further includes a determination unit configured to determine if the SIM swap information for the time interval as defined in the received request is stored in a storage unit. The system further includes an extraction unit configured to retrieve the SIM swap information for the time interval from the storage unit in response to determining the SIM swap information being stored in the storage unit.
[0017] In another aspect of the present invention, a User Equipment (UE) is disclosed. One or more primary processors communicatively coupled to one or more processors. The one or more primary processors coupled with a memory. The memory stores instructions which when executed by the one or more primary processors causes the UE to transmit the request for checking Subscriber Identity Module (SIM) swap for the time interval to the one or more processors via an entity gateway. Further, the UE transmits an attachment information pertaining to the UE including the SIM to a first network element.
[0018] In yet another aspect of the present invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions that, when executed by a processor. The processor is configured to receive a request pertaining to check the SIM swap for a time interval, the request received from an entity via an entity gateway, the time interval is defined by the entity. The processor is further configured to determine if the SIM swap information for the time interval as defined in the received request is stored in a storage unit. The processor is further configured to retrieve the SIM swap information for the time interval from the storage unit in response to determining the SIM swap information being stored in the storage unit.
[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 a Subscriber Identity Module (SIM) swap information, according to one or more embodiments of the present invention;
[0022] FIG. 2 is an exemplary block diagram of a system for managing the Subscriber Identity Module (SIM) swap information, according to one or more embodiments of the present invention;
[0023] FIG. 3 is an exemplary flow diagram of the system of FIG. 2, according to one or more embodiments of the present invention;
[0024] FIG. 4 is a flow diagram of a method for managing the Subscriber Identity Module (SIM) swap information, according to one or more embodiments of the present invention;
[0025] FIG. 5 is a signal flow diagram illustrating the flow for determining Subscriber Identity Module (SIM) swap and storing Subscriber Identity Module (SIM) swap information, according to one or more embodiments of the present disclosure.
[0026] FIG. 6 is a signal flow diagram illustrating the flow for managing the Subscriber Identity Module (SIM) swap information, according to one or more embodiments of the present disclosure.
[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 invention provides a system and a method for managing a Subscriber Identity Module (SIM) swap information. Initially, the SIM swap information related to an entity is retrieved from a storage unit. Utilizing the retrieved information pertaining to SIM swap the entity prevents the SIM swap fraud by adding confirmation and rechecking before completing a financial transaction. Additionally, the entity can also be notified about attempted fraudulent transactions. In order to check the SIM swap of any recent SIM pairing change related to the entity, the proposed system is designed in such a way that the performance of the one or more network elements is not compromised.
[0032] Referring to FIG. 1, FIG. 1 illustrates an exemplary block diagram of an environment 100 for managing the Subscriber Identity Module (SIM) swap information, according to one or more embodiments of the present invention. The environment 100 includes, a User Equipment (UE) 102, a server 104, a network 106 and a system 108. The UE 102 aids a user of a corresponding entity to interact with the system 108 to transmit a request pertaining to the SIM swap for a time interval via an entity gateway. The time interval is defined in the request transmitted by the UE 102.
[0033] For the purpose of description and explanation, the description will be explained with respect to one or more user equipment’s (UEs) 102, or to be more specific will be explained with respect 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. Each of the at least one UE 102 namely the first UE 102a, the second UE 102b, and the third UE 102c is configured to connect to the server 104 via the network 106.
[0034] In an embodiment, each of the first UE 102a, the second UE 102b, and the third UE 102c 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 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.
[0036] 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.
[0037] 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, a processor 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.
[0038] The environment 100 further includes the system 108 communicably coupled to the server 104 and each of the first UE 102a, the second UE 102b, and the third UE 102c via the network 106. The system 108 is adapted to be embedded within the server 104 or is embedded as the 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 managing the Subscriber Identity Module (SIM) swap information, according to one or more embodiments of the present invention.
[0041] As per the illustrated and preferred embodiment, the system 108 for managing the Subscriber Identity Module (SIM) swap information, the system 108 includes one or more processors 202, a memory 204, a storage unit 206, a first network element 216 and a second network element 218.
[0042] The one or more processors 202 includes a receiving unit 208, a determination unit 210, an extraction unit 212, and a comparison unit 214. 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. However, it is to be noted that the system 108 may include multiple processors as per the requirement and without deviating from the scope of the present disclosure. Among other capabilities, the processor 202 is configured to fetch and execute computer-readable instructions stored in the memory 204.
[0043] As per the illustrated embodiment, the processor 202 is configured to fetch and execute computer-readable instructions stored in the memory 204 as the memory 204 is communicably connected to the processor 202. The memory 204 is 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 check SIM swap for a time interval as defined by an entity via UE 102 and manage the SIM swap information. 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 information pertaining to the SIM swap for multiple time interval is stored in the storage unit 206. In particular, whenever the UE 102 (as shown in FIG. 1) is attached to the system 108, the storage unit 206 stores the attachment information of the UE 102 related to a first-time attachment and the re-attachment. The attachment information related to the first-time attachment of the UE 102 includes, at least one of, an International Mobile Equipment Identity (IMEI), an International Mobile Subscriber Identity (IMSI), a Mobile Station International Subscriber Directory Number (MSISDN). The attachment information related to the re-attachment of the UE 102 includes at least one of, timestamp of the latest SIM swap, change in International Mobile Subscriber Identity (IMSI), change in International Mobile Equipment Identity (IMEI), timestamp of last Mobile Station International Subscriber Directory Number (MSISDN) retrieved.
[0045] The Subscriber Identity Module (SIM) card is an Integrated Circuit (IC) intended to securely store an International Mobile Subscriber Identity (IMSI) number and its related key, which are used to identify and authenticate the subscribers of user equipment such as mobile phones and laptops.
[0046] The International Mobile Equipment Identity (IMEI) number is a unique 15–17-digit serial number which is used by service providers to uniquely identify the valid user equipment. Each user equipment such as a mobile phone is identified by the IMEI number.
[0047] International Mobile Subscriber Identity (IMSI) is a unique number automatically generated and stored in the SIM. IMSI identifies every mobile phone subscriber on a mobile communication network.
[0048] The Mobile Station International Subscriber Directory Number (MSISDN) is a unique identifier assigned to each user equipment such as a mobile device in a (Global System for Mobile Communications) GSM network. An MSISDN is a phone number associated with a Subscriber Identity Module (SIM) card which is utilized to call or send a Short Messaging Service (SMS).
[0049] The storage unit 206 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 storage unit 206 types are non-limiting and may not be mutually exclusive e.g., the database can be both commercial and cloud-based, or both relational and open-source, etc.
[0050] The attachment information pertaining to the UE 102 including the SIM is initially received at a first network element 216 of the system 108. The first network element 216 is one of, but not limited to, a Mobility Management Entity (MME) and Access and Mobility Management Function (AMF).
[0051] The Mobility Management Entity (MME) is a key component of the standards-defined Evolved Pack Core (EPC) for a Long-Term Evolution (LTE). It provides mobility session management for the LTE network and supports subscriber authentication, roaming and handovers to other networks. The Access and Mobility Management Function (AMF) is part of the 3rd Generation Partnership Project (3GPP) 5G Architecture. The primary task of the AMF includes at least one of, but not limited to, registration management, connection management, reachability management, mobility management and various functions relating to security and access management and authorization.
[0052] Further, the attachment information is received by the second network element 218 of the system 108 from the first network element. The second network element 218 is one of, but not limited to, a Home Subscriber Server (HSS) and a Unified Data Management (UDM). Thereafter, the second network element 218 transmits a request to transmit the attachment information to the comparison unit 214.
[0053] The Home Subscriber Server (HSS) serves as the primary database repository of subscriber information within a Long Term Evolution (LTE)/ Evolved Packet Core (EPC) or IP Multimedia Subsystem (IMS) network core. The Unified Data Management (UDM) manages subscriber information data in a single centralized element. UDM technology is similar to the 4G network's Home Subscriber Server (HSS) but is cloud-native and designed for 5G specifically.
[0054] In an embodiment, in order to store the SIM swap information in the storage unit 206, the comparison unit 214 of the processor 202 compares the attachment information related to the first-time attachment of the UE 102 and the re-attachment of the UE 102 to determine if the attachment information and the re-attachment is one of identical or different. In an embodiment, the attachment information related to the first-time attachment and the re-attachment is different if one of, the International Mobile Equipment Identity (IMEI), the International Mobile Subscriber Identity (IMSI) and the Mobile Station International Subscriber Directory Number (MSISDN) of the Subscriber Identity Module (SIM) related to the re-attachment is different from the IMEI, IMSI, and MSISDN related to the first-time attachment after the SIM swap.
[0055] After comparing the attachment information of the first-time attachment with the attachment information of the re-attachment, the comparison unit 214 determines if the attachment information of the re-attachment is different. In case, the attachment information of the re-attachment is different compared to the attachment information of the first-time attachment, then the storage unit 206 stores the attachment information being different as the SIM swap information. In an alternate embodiment, the comparison unit 214 is one of but not limited to, a SIM Swap Application Programming Interface (API) Data collector (SSA DC).
[0056] In an embodiment, prior to receiving a request by the processor 202 pertaining to check the SIM swap for the time interval as defined in the received request from the entity utilizing the UE 102 via the entity gateway, the entity gateway authenticates the entity. The entity gateway authenticates the entity by utilizing an Authentication key (Authkey), also known as an Application Programming Interface (API) key or access token.
[0057] The entity gateway is a network node used in telecommunications that connects two networks with different communication protocols together. For example, the entity gateway is an API gateway which acts as a mediator between UE 102 and the system 108. The API gateway is a software layer that functions as a single endpoint for various APIs performing tasks such as request composition, routing, and protocol translations.
[0058] The entity is at least one of, but not limited to, a third-party application function entity, an application, a developer, and an enterprise. Subsequent to the authentication of the entity, the authorized entity is configured to transmit the request to the receiving unit 208 of the processor 202 via the UE 102 in order to check the SIM swap of a SIM user for the time interval defined by the entity via the entity gateway. In an alternate embodiment, the entity is configured to transmit a SIM swap API call to the processor 202 via a communication protocol in order to check the SIM swap of the SIM user for the time interval defined by the entity. The communication protocol includes, but not limited to, Session Initiation Protocol (SIP), System Information Block (SIB) protocol, Transmission Control Protocol (TCP), User Datagram Protocol (UDP), File Transfer Protocol (FTP), Hypertext Transfer Protocol (HTTP), Simple Network Management Protocol (SNMP), Internet Control Message Protocol (ICMP), Hypertext Transfer Protocol Secure (HTTPS) and Terminal Network (TELNET).
[0059] In an embodiment, the receiving unit 208 of the processor 202 is configured to receive a request pertaining to the SIM swap from an entity utilizing the UE 102 via the entity gateway in order to check the SIM swap for the time interval as defined by the entity subsequent to the authentication of the entity with respect to the entity gateway. In an alternate embodiment, the receiving 208 of the processor 202 is configured to receive the SIM swap API call via the entity gateway in order to check the SIM swap. The entity gateway is at least one of, an API gateway that acts as the entry point for the API calls which represents the entities request to retrieve information pertaining to the SIM swap.
[0060] In an embodiment, the determination unit 210 of the processor 202 is configured to determine whether the SIM swap information for the time interval as defined in the received request is stored in the storage unit 206. In particular, the determination unit 210 checks for the SIM swap information in the storage unit 206 based on the time interval defined by the entity.
[0061] In an embodiment, the extraction module 212 of the processor 202 is configured to retrieve the SIM swap information for the time interval as defined in the received request from the storage unit 206 in response to determining by the determination unit 210 that the SIM swap information is being stored in the storage unit 206. In an alternate embodiment, based on the SIM swap API call or the SIM swap request, the extraction module 212 is configured to retrieve timestamp and location of the SIM swap performed within the time interval for the SIM registered to a network provider.
[0062] In an alternate embodiment, the determination unit 210 and the extraction module 212 may be a combined unit such as one of but not limited to, a SIM Swap Application Programming Interface (API) Exposure Function (SSA EF).
[0063] Subsequent to retrieving the SIM swap information from the storage unit 206 for the time interval as defined by the entity, the receiving unit 208 transmits the retrieved SIM swap information for the time interval to the entity via the entity gateway. The retrieved SIM swap information includes details such as but not limited to, SIM swap status, timestamp and location of the SIM swap performed for the SIM registered to the network provider. In an alternate embodiment, a report is generated by the extraction module 212 pertaining to the SIM swap information retrieved from the storage unit 206 for the time interval as defined by the entity and thereafter, the receiving unit 208 transmits the generated report to the entity via the entity gateway.
[0064] The receiving unit 208, the determination unit 210, the extraction unit 212, and the comparison unit 214 in an exemplary embodiment, are 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 202. In such examples, the system 108 may comprise the memory 204 storing the instructions and the processing resource to execute the instructions, or the memory 204 may be separate but accessible to the system 108 and the processing resource. In other examples, the processor 202 may be implemented by electronic circuitry.
[0065] FIG. 3 illustrates an exemplary block diagram of an architecture for the system 108, according to one or more embodiments of the present invention. More specifically, FIG. 3 illustrates the system 108 configured for checking and managing the SIM swap information. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the UE 102 for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.
[0066] FIG. 3 shows communication between the UE 102 and the system 108. For the purpose of description of the exemplary embodiment as illustrated in FIG. 3, the UE 102 uses network protocol connection to communicate with the system 108. In an embodiment, the network protocol connection is the establishment and management of communication between the UE 102 and the system 108 over the network 106 (as shown in FIG. 1) using a specific protocol or set of protocols. The network protocol connection includes, but not limited to, Session Initiation Protocol (SIP), System Information Block (SIB) protocol, Transmission Control Protocol (TCP), User Datagram Protocol (UDP), File Transfer Protocol (FTP), Hypertext Transfer Protocol (HTTP), Simple Network Management Protocol (SNMP), Internet Control Message Protocol (ICMP), Hypertext Transfer Protocol Secure (HTTPS) and Terminal Network (TELNET).
[0067] In an embodiment, the UE 102 includes a primary processor 302, a memory 304, and a user interface 306. In alternate embodiments, the UE 102 may include more than one primary processor 302 as per the requirement of the network 106. The primary processor 302, 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.
[0068] In an embodiment, the primary processor 302 is configured to fetch and execute computer-readable instructions stored in the memory 304. The memory 304 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 check for the SIM swap for the time interval as defined by the entity via UE 102. The memory 304 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.
[0069] In one embodiment, the UE 102 is configured to transmit an attachment information including the SIM to the first network element 216. The UE 102 is further configured to transmit the request to the one or more processors 202 using a user interface 306 for checking SIM swap for the time interval to the one or more processors 202 via the entity gateway.
[0070] In an embodiment, the user interface 306 of the UE 102 includes a variety of interfaces, for example, a graphical user interface, a web user interface, a Command Line Interface (CLI), and the like. The user interface module 306 is configured to allow the entity to manage the request for checking SIM swap for the time interval. The UE 102 transmits the request for checking SIM swap for the time interval to the processor 202 via the user interface 306.
[0071] Initially, whenever the UE 102 is first-time attached to the system 108, the storage unit 206 stores the attachment information of the UE 102 related to the first-time attachment. Further, whenever the UE 102 is second-time attached to the system 108, the system 108 infers as the re-attachment of the UE 102. The storage unit 206 stores the attachment information of the UE 102 related to the re-attachment as the re-attachment information based on the comparison of the attachment information of the first-time attachment of the UE 102 with the re-attachment information of the UE 102, the comparison is performed by the comparison unit 214. The storage unit 206 stores the SIM swap information in response to the attachment information being different to the re-attachment information. For example, when the entity is first-time attached to the system 108, the attachment information such as IMEI, IMSI, MSISDN related to the UE 102 is stored in the storage unit 206. Further, when the entity is second-time attached to the system 108, the re-attachment information including at least one of, but not limited to, change in the IMEI, change in the IMSI, change in the MSISDN related to the UE 102 is stored in the storage unit 206. In particular, as the UE 102 is second-time attached to the system 108, the system 108 determines the change in the IMEI of the UE 102 when compared with the IMEI related to the first-time attachment. This change in the IMEI of the UE 102 when the UE 102 is second-time attached to the system 108 is stored as the SIM swap information in the storage unit 206. Additionally, the storage unit 206 also stores the time stamp related to the SIM swap.
[0072] When the entity transmits the request for checking the SIM swap for the defined time interval from the user interface 306 of the UE 102 via the entity gateway, the receiving unit 208 receives the request via the entity gateway. Further, the determination module 210 checks for the SIM swap information for the defined time interval in the received request in order to determine whether the SIM swap information for the defined time interval is stored in the storage unit 206. Based on the determination of the SIM swap information being stored in the storage unit 206, the extraction module 212 retrieves the SIM swap information for the defined time interval from the storage unit 206 and the receiving unit 208 transmits the retrieved SIM swap information related to the defined time interval to the UE 102 of the entity via the entity gateway.
[0073] For example, let us assume the entity such as the network operator is checking whether the SIM swap for a plurality of customers has occurred without defining the time interval. In this scenario, the system 108 will provide the network operator with the SIM swap information related to the plurality of customers. In other words, the system 108 will provide the historical data as well as current data related to the SIM swap information of the plurality of customers to the network operator. The historical data as well as the current data related to the SIM swap information will be displayed as a list on the user interface 306 of the network operator.
[0074] Further, if the network operator needs to check the recent SIM swap information for the plurality of customers i.e, for example, within 24 hours, then the network operator may face one or more issues such as at least one of, but not limited to, more time required for checking the recent SIM swap information. In order to identify the recent SIM swap information for the plurality of customers among the list of the historical data as well as the current data related to the SIM swap information, of the plurality customers is a cumbersome task for the network operators. In order to overcome the one or more issues faced by the network operators, the system 108 allows the network operators to define the time interval based on which the system 108 will provide the network operator with the SIM swap information related to the plurality of customers. For example, if the defined time interval is for 24 hours, then the system 108 will provide the network operator with the SIM swap information related to the plurality of customers that has occurred within last 24 hours. Advantageously, the one or more issues faced by the network operators are rectified by defining the time interval which leads to reduction in a time period for notifying the plurality of customers regarding the SIM swap.

[0075] FIG. 4 is a flow diagram of a method 400 for managing the Subscriber Identity Module (SIM) swap information, according to one or more embodiments of the present invention. For the purpose of description, the method is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
[0076] At step 402, the method 400 includes the step of receiving a request pertaining to check the SIM swap for a time interval, the request received from an entity via an entity gateway, the time interval is defined by the entity. In one embodiment, receiving unit 208 of the processor 202 is configured to receive the request pertaining to check the SIM swap for a time interval defined by the entity utilizing the UE 102 (as shown in FIG. 1) via the entity gateway in order to check and further retrieve information pertaining to the SIM swap from the storage unit 206 subsequent to the authentication of the entity. In an alternate embodiment, the SIM swap check API call is received at the receiving unit 208 of the processor 202 to check and further retrieve information pertaining to the SIM swap from the storage unit 206.
[0077] At step 404, the method 400 includes the step of determining if the SIM swap information for the time interval as defined in the received request is stored in a storage unit 206. In one embodiment, the determination unit 210 of the processor 202 is configured to determine whether the SIM swap information for the time interval as defined in the received request is stored in the storage unit 206. For example, whenever the UE 102 is first time attached to the system 108, the system 108 infers as the first-time attachment and the attachment information of the UE 102 is stored in the storage unit 206 which includes at least one of, the IMEI, the IMSI, and the MSISDN. Let us assume the SIM swap is done by the fraudster who had managed to obtain an entity/user phone number and transferred the user calls/messages to the fraudster’s SIM card within the fraudster’s UE. Further, when the fraudster’s UE attaches to the system 108 using the phone number of the user, the processor 202 infers the fraudster’s UE attachment as the re-attachment and the re-attachment information pertaining to the fraudster’s UE is stored in the storage unit 206 which includes at least one of, but not limited to, the change in the IMEI, change in the IMSI, and the MSISDN of the fraudsters UE. The comparison unit 214 determines that the attachment information related to the first-time attachment and the re-attachment is different and transmits response to the storage unit 206 in order to store the changes pertaining to the re-attachment information as the SIM swap information based on the attachment information being different to the re-attachment information. Further, when the request is received for retrieving the SIM swap information, the determination unit 210 checks whether the information pertaining to the SIM swap for the time interval as defined by the entity is available in the storage unit 206 corresponding to the received request. This check is done without communicating with at least one of, first network element 216 and the second network element 218.
[0078] In an alternate embodiment, a SIM Swap Application Programming Interface (API) is used to provide the entity an ability to obtain information of any recent SIM swap or SIM pairing change related to a mobile account of the user. Further, the SIM swap API provides functionalities such as, a post check operation and a path operation. In the post check operation the SIM Swap API checks if the SIM swap has been performed in the past during the time interval as defined by the entity. The time interval is provided by a variable ‘maxAge’ attribute. In the path operation, the SIM swap API checks for the path in which the SIM swap is performed. The path operation is performed after execution of the post check operation.
[0079] At 406, the method 400 includes the step of retrieving the SIM swap information for the time interval from the storage unit 206 in response to determining the SIM swap information being stored in the storage unit 206. Based on the response of determination by the determination unit 210 related to the availability of the SIM swap information in the storage unit 206 for the time interval as defined by the entity in the received request, the extraction unit 212 of the processor 202 is configured to retrieve SIM swap information for the time interval as defined by the entity from the storage unit 206.
[0080] Further, subsequent to retrieving the SIM swap information from the storage unit 206 for the time interval as defined by the entity, the receiving unit 208 transmits the retrieved SIM swap information to the entity via the entity gateway. Advantageously, utilizing the retrieved SIM swap information, the entity prevents the fraud of the SIM swap.
[0081] FIG. 5 is a signal flow diagram illustrating the flow for determining Subscriber Identity Module (SIM) swap and storing Subscriber Identity Module (SIM) swap information, according to one or more embodiments of the present disclosure.
[0082] At step 502, using the UE 102 the entity attaches to the first network element 216. Further, the attachment information pertaining to the UE 102 including the SIM is transmitted to the first network element 216. In particular, the attachment information is for one of a first-time attachment or for re-attachment. For example, the first-time attachment pertains to when the UE 102 is first time connected to the first network element 216 such as the MME or the AMF.
[0083] In one embodiment, when the UE 102 is first time attached to the first network element 216, then it is inferred as the UEs first attach.
[0084] At step 504, the first network element 216 receives the attachment information and further transmits the received attachment information to the second network element 218. In particular, the attachment information is for one of the first-time attachment information or the re-attachment information.
[0085] In one embodiment, in case of UEs the first attach or a fresh attach, an Update Location requests (ULR) message is triggered by the first network element 216. The ULR message transmits the identity and roaming information pertaining to the UE 102 to the second network element 218. The ULR message includes, at least one of, the IMEI of the UE 102. The ULR message is related to the first-time attachment information of the UE 102. The ULR message is transmitted by the first network element 216 to the second network element 218.
[0086] In another embodiment, in case of re-attachment of the UE 102 or when there is a change in the IMEI of the UE 102, a Notification Request (NOR) message is triggered by the first network element 216. The NOR message is to inform the second network element 218 about change in UEs 102 information. The NOR message includes, at least one of, the change in IMEI of the UE 102. The NOR message is related to the re-attachment information of the UE 102. The NOR message is transmitted by the first network element 216 to the second network element 218.
[0087] In another embodiment, a Mobile Application Part (MAP) location update request is transmitted by the first network element 216 to the second network element 218 in order to provide the location of the UE 102 to the second network element 218 or to update the location information stored in the second network element 218. In yet another embodiment, when the first network element 216 is the AMF, the first network element 216 transmits an AMF Third Generation Partnership Project (3GPP) Registration/ Registration Modification request in order to register the UE 102 to the second network element 218.
[0088] In yet another embodiment, the IMEI is revived by the second network element 218 from at least one of, but not limited to, the ULR message, the NOR message, the MAP location update request, and the AMF 3GPP Registration Request.
[0089] At step 506, the second network element 218 receives the attachment information from the first network element 216 and further transmits a request such as a Hypertext Transfer Protocol (HTTP) request ADD trigger to transmit the attachment information to the comparison unit 214 such as the SSA DC. The ADD trigger or ADD message is transmitted in case of the ULR message, the NOR message, the MAP location update request, and the AMF 3GPP Registration Request. In one embodiment, subsequent to receiving the attachment information as the IMEI from the at least one of the, the ULR message, the NOR message, the MAP location update request, and the AMF 3GPP Registration Request, the second network element 218 transmits the HTTP request to the SSA DC.
[0090] At step 508, the comparison unit 214 initially receives the attachment information and transmits a request to the storage unit 206 in order to store attachment information as a triplet information when the attachment information is related to the first-time attachment of the UE 102. The triplet information includes IMSI, IMEI and MSISDN of the UE 102. Alternatively, when the attachment information is related to the re-attachment of the UE 102, the comparison unit 214 compares the attachment information related to the first-time attachment with the re-attachment and identifies whether the attachment information of the first-time attachment and re-attachment information is identical or different. Based on the identification of the attachment information being different to the re-attachment information, the comparison unit 214 transmits a request to the storage unit 206 in order to store the SIM swap information.
[0091] In one embodiment, when the IMEI of the UE 102 received from the network element 216 via at least one of, the ULR message, the NOR message, the MAP location update request, and the AMF 3GPP Registration Request is different based on the comparison with the IMEI which was pre stored in the storage unit 206, then this change in the IMEI is stored as the SIM swap information.
[0092] At step 510, subsequent to storing the SIM swap information or the attachment information related to the first-time attachment and the re-attachment, the storage unit 206 transmits a response related to the storage of the SIM swap information or the attachment information to the first network element 216 via the comparison unit 214 and the second network element 218.
[0093] FIG. 6 is a signal flow diagram illustrating the flow for managing the Subscriber Identity Module (SIM) swap information, according to one or more embodiments of the present disclosure.
[0094] At step 602, the entity initiates a request pertaining to check SIM swap for a time interval using the UE 102 via a gateway such as an entity gateway subsequent to the authentication of the entity. Further, the request is transmitted to the gateway.
[0095] At step 604, from the gateway the request is forwarded to the SSA EF of the processor 202 to check for the availability of the SIM swap information in the storage unit 206 for the time interval defined by the entity in the received request.
[0096] At step 606, the SSA EF transmits a request to the storage unit 206 in order to retrieve the SIM swap information subsequent to determining that the SIM swap information requested by the entity for the time interval is available in the storage unit 206.
[0097] At step 608, the storage unit 206 responds to the request transmitted by the SSA EF by transmitting the SIM swap information for the time interval defined by the entity from to the SSA EF.
[0098] At step 610, subsequent to the retrieval of the SIM swap information from the storage unit 206, the SSA EF transmits the retrieved SIM swap information for the time interval as a response to the gateway.
[0099] At step 612, the gateway transmits the SIM swap information received from the SSA EF to the entity.
[00100] 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 a request pertaining to the SIM swap for a time interval, the request received from an entity via an entity gateway, wherein the time interval is defined by the entity. The processor 202 is further configured to determine if the SIM swap information for the time interval as defined in the received request is stored in a storage unit 206. The processor 202 is further configured to retrieve the SIM swap information for the time interval from the storage unit 206 in response to determining the SIM swap information being stored in the storage unit 206.
[00101] 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.
[00102] The present disclosure provides technical advancement related to checking a recent SIM swap related to the users or subscribers in defined time period. The check for SIM swap is performed offline on data made available within the microservices managed by the processor. The fraudulent activities occurring due to the SIM swap are detected even before occurrence of any fraudulent transaction. The network operators retrieve the SIM swap information let assume SIM swap within 24 hours and utilize the SIM swap information to prevent the fraud of SIM swap by adding more confirmation and rechecks before completing any financial transaction. The SIM swap information is notified to the user based on demand.
[00103] 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

[00104] Environment - 100;
[00105] User Equipment (UE) - 102;
[00106] Server - 104;
[00107] Network- 106;
[00108] System -108;
[00109] Processor - 202;
[00110] Memory - 204;
[00111] Storage unit – 206;
[00112] Receiving unit– 208;
[00113] Determination unit – 210;
[00114] Extraction unit– 212;
[00115] Comparison unit – 214;
[00116] First network element – 216;
[00117] Second network element – 218;
[00118] Primary processor- 302;
[00119] Memory- 304;
[00120] User Interface – 306.
,CLAIMS:CLAIMS
We Claim:
1. A method (400) of managing a Subscriber Identity Module (SIM) swap information, the method (400) comprising the steps of:
receiving, by one or more processors (202), a request pertaining to check the SIM swap for a time interval, the request received from an entity via an entity gateway, wherein the time interval is defined by the entity;
determining, by the one or more processors (202), if the SIM swap information for the time interval as defined in the received request is stored in a storage unit (206); and
retrieving, by the one or more processors (202), the SIM swap information for the time interval from the storage unit (206) in response to determining the SIM swap information being stored in the storage unit (206).

2. The method (400) as claimed in claim 1, wherein on retrieving the SIM swap information for the time interval from the storage unit (206), the one or more processors (202) is further configured to perform the step of:
transmitting, the retrieved SIM swap information related to the time interval to the entity via the entity gateway.

3. The method as claimed in claim 1, wherein the entity is at least one of a third-party application function entity, an application, a developer, and an enterprise.

4. The method (400) as claimed in claim 1, wherein the request pertaining to check the SIM swap for the time interval is received subsequent to authentication of the entity with respect to the entity gateway.

5. The method (400) as claimed in claim 1, wherein upon authentication of the entity, the entity is configured to transmit a SIM swap request to the one or more processors (202) via a communication protocol.

6. The method (400) as claimed in claim 5, wherein based on the SIM swap request, the one or more processors (202) is configured to one of, retrieve timestamp and location of the timestamp of a latest SIM swap performed for the SIM registered to a network provider and check the SIM swap for the time interval

7. The method (400) as claimed in claim 1, wherein step of determining, by the one or more processors (202), if the SIM swap information for the time interval as defined in the received request is stored in a storage unit (206), include the steps of:
receiving, at a first network element (216), an attachment information pertaining to a User Equipment (UE) (102) including the SIM, wherein the attachment information is for one of a first-time attachment and for a re-attachment;
receiving, at a second network element (218), the attachment information from the first network element (216);
transmitting, by the second network element (218), a request to transmit the attachment information to the one or more processors (202);
comparing, by the one or more processors (202), the attachment information related to the first-time attachment and the re-attachment to determine if the attachment information and re-attachment is one of identical or different; and
storing, by the one or more processors (202), the SIM swap information in response to the attachment information being different to the re-attachment information.

8. The method (400) as claimed in claim 7, wherein the attachment information related to the first-time attachment includes International Mobile Equipment Identity (IMEI), International Mobile Subscriber Identity (IMSI), Mobile Station International Subscriber Directory Number (MSISDN).

9. The method (400) as claimed in claim 7, wherein the attachment information related to the re-attachment includes timestamp of the latest SIM status change, change in International Mobile Subscriber Identity (IMSI), change in International Mobile Equipment Identity (IMEI), timestamp of last Mobile Station International Subscriber Directory Number (MSISDN) retrieved.

10. The method (400) as claimed in claim 7, wherein the attachment information related to the first-time attachment and the re-attachment is different if one of, International Mobile Equipment Identity (IMEI), International Mobile Subscriber Identity (IMSI) and Mobile Station International Subscriber Directory Number (MSISDN) of the Subscriber Identity Module (SIM) related to the re-attachment is different from the IMEI, the IMSI, and the MSISDN related to the first-time attachment after the SIM swap

11. A system (108) for managing a Subscriber Identity Module (SIM) swap information, the system (108) comprising:
a receiving unit (208), configured to, receive, a request pertaining to check the SIM swap for a time interval, the request received from an entity via an entity gateway, wherein the time interval is defined by the entity;
a determination unit (210), configured to, determine, if the SIM swap information for the time interval as defined in the received request is stored in a storage unit (206); and
an extraction unit (212), configured to, retrieve, the SIM swap information for the time interval from the storage unit (206) in response to determining the SIM swap information being stored in the storage unit (206).

12. The system (108) as claimed in claim 11, wherein on retrieving the SIM swap information for the time interval from the storage unit (206), the receiving unit (208) is further configured to:
transmit, the retrieved SIM swap information to the entity via the entity gateway.

13. The system (108) as claimed in claim 11, wherein the entity is at least one of a third-party application function entity, an application, a developer, and an enterprise.

14. The system (108) as claimed in claim 11, wherein the request pertaining to check the SIM swap is received subsequent to authentication of the entity with respect to the entity gateway.

15. The system (108) as claimed in claim 14, wherein upon authentication of the entity, the entity is configured to transmit a SIM swap request to the receiving unit (208) via a communication protocol.

16. The system (108) as claimed in claim 15, wherein based on the SIM swap request, the extraction module (212) is configured to one of, retrieve timestamp and location of the timestamp of a latest SIM swap performed for the SIM registered to a network provider and check the SIM swap for the time interval.

17. The system (108) as claimed in claim 11, wherein to determine, if the SIM swap information for the time interval as defined in the received request is stored in a storage unit (206), the system (108) comprises:
a first network element (216), configured to, receive, an attachment information pertaining to a user equipment including the SIM, wherein the attachment information is for one of a first-time attachment and for re-attachment;
a second network element (218), configured to:
receive, the attachment information from the first network element (216); and
transmit a request to transmit the attachment information to a comparison unit (214);
a comparison unit (214), configured to:
compare, the attachment information related to the first-time attachment and the re-attachment to determine if the attachment information and re-attachment is one of identical and different; and
a storage unit (206), configured to, store, the SIM swap information in response to the attachment information being different to the re-attachment information.

18. The system (108) as claimed in claim 17, wherein the attachment information related to the first-time attachment includes International Mobile Equipment Identity (IMEI), International Mobile Subscriber Identity (IMSI), Mobile Station International Subscriber Directory Number (MSISDN).

19. The system (108) as claimed in claim 17, wherein the attachment information related to the re-attachment includes timestamp of the latest SIM swap, change in International Mobile Subscriber Identity (IMSI), change in International Mobile Equipment Identity (IMEI), timestamp of last Mobile Station International Subscriber Directory Number (MSISDN) retrieved.

20. The system (108) as claimed in claim 17, wherein the attachment information related to the first-time attachment and the re-attachment is different if one of International Mobile Equipment Identity (IMEI), International Mobile Subscriber Identity (IMSI) and Mobile Station International Subscriber Directory Number (MSISDN) of the Subscriber Identity Module (SIM) related to the re-attachment is different from the IMEI, IMSI, and MSISDN related to the first-time attachment post SIM swap.

21. 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 (304), wherein said memory (304) stores instructions which when executed by the one or more primary processors (302) causes the UE (102) to:
transmit, the request for checking Subscriber Identity Module (SIM) swap for the time interval to the one or more processors (202) via an entity gateway;
transmit, an attachment information pertaining to a user equipment (102) including the SIM to a first network element (216),
wherein, the one or more processors (202) is configured to perform the steps as claimed in claim 1.