TECHNICAL FIELD
[0001] The subject matter described herein, in general, relates to user identification and, in particular, relates to user identification based on subscriber identity module (SIM) information.
BACKGROUND [0002] Compact computer implemented applications, also known as mobile applications are increasingly used in user devices. The mobile applications provide various user preference based services and functionalities. However, most of the mobile applications desire a user to register and create a user profile so that the mobile application can authenticate the user and obtain certain user preferences.
BRIEF DESCRIPTION OF DRAWINGS [0003] The detailed description is provided with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the drawings to reference like features and components. [0004] Fig. 1 illustrates an exemplary network environment for user identification, according to an implementation of the present subject matter.
[0005] Fig. 2 illustrates an exemplary network entity for user identification, according to an implementation of the present subject matter.
[0006] Fig. 3 illustrates an exemplary network entity for user identification, according to another implementation of the present subject matter. [0007] Fig. 4 illustrates an exemplary method for user profile identification, according to an implementation of the present subject matter.

[0008] Fig. 5 illustrates an exemplary method for user identification, according to another implementation of the present subject matter.
DETAILED DESCRIPTION [0009] The present subject matter relates to methods and systems for user profile identification. The user identification may be carried out using subscriber identity module (SIM) information at the operator end.
[0010] Mobile applications request users to enter personal details, such as mobile number, age, gender and address for the purposes of authentication and identification. Such details are also used to provide customized services to the users. However, it is not always possible for the users to enter all the data requested by the mobile application, as not all the users are tech-savvy. Also, some users may either take too much time to fill in the details or may not wish to enter the details at all. Thus, it becomes cumbersome for the application to gather the desired data, and provide customized services to the users.
[0011] Further, in case the application has to register or authenticate the user, the application may use multiple level of authentication and user inputs such as one-time password (OTP) and security personal identification number (PIN). Thus, there may be some unavoidable delay in providing customized services to the users. [0012] To this end, techniques for automatic user profile identification for mobile applications are described herein. The various examples of the present subject matter disclose techniques for identifying a user of mobile application, without an input from the user.
[0013] In an implementation of the present subject matter, upon user initiation of the mobile application, the mobile application may capture unique SFM information from SFM of the user device, for obtaining user information to register the user with the mobile application. To obtain the user information, the mobile application may

then send a user profile request to a network service provider. The user profile request may include the unique SIM information associated with the user device. [0014] The network service provider may search a repository for data corresponding to the unique SIM information, in response to the user profile request for user profile data received along with the unique SIM information. The network service provider may further, extract user profile data from the information searched for the unique SIM information, and transmit the user profile data to the user device. [0015] The user profile data received by the user device may be used by the mobile application to generate user account, by automatically filling up user's personal information at desired locations, and automatically registering the user. [0016] The present subject matter eases the user information gathering process for the mobile applications by utilizing the user profile data received from the network service provider, for authentication and identification. Also, the dependence of the mobile application on user inputs for security has been addressed, as the communication between the mobile application on user device and the network service provider is independent of user input and carried out using secure telecommunication protocols.
[0017] The above techniques are further described in conjunction with the following figures. It should be noted that the description and figures merely illustrate the principles of the present subject matter. It will thus be appreciated that those skilled in the art will be able to devise various arrangements that, although not explicitly described or shown herein, embody the principles of the present subject matter and are included within its spirit and scope. Furthermore, all examples recited herein are principally intended expressly to be only for pedagogical purposes to aid the reader in understanding the principles of the present subject matter and the concepts contributed by the inventor(s) to furthering the art, and are to be construed as being without limitation to such specifically recited examples and conditions. Moreover, all statements herein reciting principles, aspects, and embodiments of the

present subject matter, as well as specific examples thereof, are intended to encompass equivalents thereof.
[0018] It will also be appreciated by those skilled in the art that the words during, while, and when, as used herein, are not exact terms that mean an action takes place instantly upon an initiating action but that there may be some small but reasonable delay, such as a propagation delay, between the initial action and the reaction that is initiated by the initial action. Additionally, the word "connected" is used throughout for clarity of the description and can include either a direct connection or an indirect connection.
[0019] Fig. 1 illustrates a communication network environment 100 implementing user profile identification operator server 102 for identifying users of user devices 104-1, 104-2, 104-3, ..., 104-N, according to an embodiment of the present subject matter. The user devices 104-1, 104-2, 104-3, ..., 104-N, may be collectively referred to as user devices 104. In the communication network environment 100, the user devices 104 communicate with each other through a communication network 106. The user devices 104 also interact with various network entities, for example, to avail various communication services or to communicate with other user devices 104, through the communication network 106. The operator server 102 may further be communicatively coupled to a repository 108. The repository 108 may contain information of all the subscribers or users. The repository may include user information corresponding to SFM card issued by an operator server 102. For ease of understanding, the repository 108 has been illustrated as an external module, however, it may be appreciated that the repository 108 may be internal to the operator server 102.
[0020] The user devices 104 may include, fixed/wired telephones, handheld devices, tablet computers, mobile phones, PDAs, smartphones, and the like. Each of the user devices 104 works on a communication protocol as defined by a communication network 106 to which the user device 104 is coupled.

[0021] The user devices 104 may include subscriber identity module (SIM) cards that securely store a unique identification information, such as International Mobile Subscriber Identity (EVISI) number and a related key used to identify and authenticate subscribers on communication network 106.
[0022] The communication network 106 may be a wireless or a wired network, or a combination thereof. Examples of such individual networks include, but are not limited to, Global System for Mobile Communication (GSM) network, Universal Mobile Telecommunications System (UMTS) network, Personal Communications Service (PCS) network, Time Division Multiple Access (TDMA) network, Code Division Multiple Access (CDMA) network, Next Generation Network (NGN), Public Switched Telephone Network (PSTN). Depending on the technology, the communication network 106 includes various network entities, such as gateways, routers; however, such details have been omitted for ease of understanding. [0023] The foregoing description is explained with reference to the user devices 104-1 and 104-n, and it will be understood that the same can be extended to other user devices as well. In order to communicate with each other, the user devices 104 connect to their respective base transceiver stations (not shown in the figure), which provide radio coverage within a cell. Multiple base transceiver stations connect to a base station controller (not shown in the figure), which provides local switching to effect handover between the base stations. The base station controller is further connected to a Mobile Switching Center (MSC) (not shown in the figure), which is responsible for allowing the different user devices 104 to communicate with each other.
[0024] In an implementation, the SIM based user device 104 captures unique SIM information from SIM in the user device 104, and transmits the unique SIM information to operator server 102 along with a user profile request, for registering the user with a mobile application on the user device 104. In an implementation, the user profile request includes a query for user profile data.

[0025] In response to receiving the user profile request for user profile data along with the unique SIM information, the operator server 102 may search a repository 108 for data corresponding to the unique SIM information, in accordance with an implementation of the present subject matter. The operator server 102 may further, extract user profile data from the information searched for the unique SIM information, and transmit the user profile data to the user device 104. The user profile data received by the user device 104 may be used by the mobile application on the user device 104 for registering the user.
[0026] In an illustration, an e-commerce mobile application installed on user device may capture IMSI number from the SIM of the user device 104, and transmit the IMSI number to the operator server along with a user profile request for registering the user and creating an account for the user.
[0027] In an example, the user profile request may include a query for user profile data, such as name of the user, age of the user, gender of the user, current location of the user, account balance of the user, historical shopping habits. [0028] In response to receiving the user profile request for the user profile data along with the IMSI, the operator server may search in device manager's (DM) repository for data corresponding to the IMSI. The device manager's (DM) repository contains a database of information corresponding to each subscriber uniquely linked to each IMSI. The operator server may further extract the user profile data from the database in device manager's (DM) repository corresponding to the IMSI received from the mobile application on the user device 104. The operator server may also share the user profile data extracted with the e-commerce mobile application on the user device 104.
[0029] The e-commerce mobile application on the user device 104 may use the user profile data received for creating user account, and providing the user with customized purchase options based on historical shopping habits, all without user input.

[0030] Fig. 2 schematically illustrates the various components of the operator server 102. In an example implementation of the present subject matter, the operator server 102 includes processor(s) 202 coupled to a memory 204. The operator server 102 further includes interface(s) 206, for example, to facilitate communication with the user device 104 and repository 108. The interface(s) 206 may include a variety of software and hardware interfaces, for example, interfaces for peripheral device(s), such as a keyboard, a mouse, an external memory, and a printer. Further, the interface(s) 206 enables the operator server 102 to communicate with other devices, such as web servers and external repositories. The interface(s) 206 can also facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example LAN, cable, etc., and wireless networks such as WLAN, cellular, or satellite. For the purpose, the interface(s) 206 may include one or more ports for connecting a number of computing devices to each other or to other server computers.
[0031] The processor(s) 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the processor(s) 202 are configured to fetch and execute computer-readable instructions stored in the memory 204.
[0032] The memory 204 may include a computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), etc., and/or non-volatile memory, such as erasable program read only memory (EPROM), flash memory, etc. [0033] Further, the memory 204 is communicatively coupled to engine(s) 208 and data 216. The engine(s) 208 includes, for example, a comparison engine 210, a profiling engine 212, and other engine(s) 214. The other engine(s) 214 may include

programs or coded instructions that supplement applications or functions performed
by the operator server 102.
[0034] The data 216 includes a SIM information 218, user profile data 220, and
other data 222. In one implementation, the SIM information 218, user profile data
220 are stored in the memory 204 in the form of look-up tables. Further, the other
data 222, amongst other things, may serve as a repository for storing data that is
processed, received, or generated as a result of the execution of one or more engines
in the engine(s) 208. Although the data 216 is shown internal to the operator server
102, it may be understood that the data 216 may reside in an external repository (not
shown in the figure), which is coupled to the operator server 102. The operator server
102 may communicate with the external repository through the interface(s) 206 to
obtain information from the data 216.
[0035] As described earlier, the operator server 102 includes a comparison engine
210. The comparison engine 210 may receive a user profile request from a user
device 104 along with a unique SFM information. The user profile request is made for
identify information corresponding to the unique SFM information. Next, the
comparison engine 210 may search the repository 108 to identify all information
corresponding to the unique SFM information.
[0036] The profiling engine 212 may extract the user profile data corresponding to
the unique SFM information, based on the search conducted by the comparison engine
210. In an example, the user profile data may include name of the user, identity proof,
biometric data, digital signature, photograph, and the like.
[0037] The profiling engine 212 may then transmit the extracted user profile data
to the user device 104, as user profile requested by the user device 104.
[0038] Fig. 3 schematically illustrates the various components of the user device
104. In an example implementation of the present subject matter, the user device 104
may include processor(s) 302 coupled to a memory 304. The user device 104 further

includes interface(s) 306, for example, to facilitate communication with the user and network entities such as operator server 102.
[0039] Further, the memory 304 is communicatively coupled to engine(s) 308 and data 316. The engine(s) 308 include, for example, a SIM engine 310, application engine 312, and other engine(s) 314. The other engine(s) 314 may include programs or coded instructions that supplement applications or functions performed by the user device 104.
[0040] The data 316 includes a SIM information 318, and other data 320. In one implementation, the SIM information 318 is stored in the memory 304 in the form of look-up tables. Further, the other data 320, amongst other things, may serve as a repository for storing data that is processed, received, or generated as a result of the execution of one or more engines in the engine(s) 308. Although the data 316 is shown internal to the user device 104, it may be understood that the data 316 may reside in an external repository (not shown in the figure), which is coupled to the user device 104. The user device 104 may communicate with the external repository through the interface(s) 306 to obtain information from the data 316. [0041] In one implementation, the user device 104 includes the application engine 312. The application engine 312 may generate user profile request for registration the user with the mobile application. The application engine 312 may further capture unique SFM information from the SFM engine 310. In an implementation, the application engine 312 corresponds to a mobile application patch on the user device 104 communicatively coupled with the mobile application, SFM engine 310, and the operator server 102. The application engine 312 may provide an additional functionality to the mobile application to get connected to the operator server 102 and securely obtain user profile data.
[0042] The application engine 312 may further transmit the user profile request for user profile data along with the unique SFM information to the operator server 102.

[0043] In response to the user profile request, the application engine 312 may receive the user profile data from the operator server 102. The application engine 312 may share the user profile data with the mobile application to enable registration of the user with the mobile application.
[0044] In yet another implementation, user profile data may be indicative of personal information related to the subscriber of the SIM in the user device 104. [0045] In yet another implementation, the user profile data may include, name of the user, address of the user, biometric data of the user, photograph of the user, preferences of the user, identity proof the user, balance in user's account, or a combination thereof.
[0046] In an example, the identity proof of the user may be government issued identity proof such as Aadhar card, passport, vote ID card, PAN card. [0047] In an implementation, the user profile data may be used by the application engine 312 for registering and account creation of the user, without any input from the user.
[0048] In another implementation, the user profile data may be used by the application engine 312 for allowing login of the user, without any input from the user. [0049] Although the network environment 100 illustrates one operator server 102, it will be appreciated that any number of operator server 102 may be connected through the network 106.
[0050] Fig. 4 illustrates an exemplary method for user profile identification using SEVI information, according to an implementation of the present subject matter. [0051] The exemplary method may be described in the general context of computer executable instructions embodied on a computer-readable medium. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, functions, etc., which perform particular functions or implement particular abstract data types. The method may also be practiced in a distributed computing environment where functions are performed

by remote processing devices that are linked through a communications network. In a distributed computing environment, computer executable instructions may be located in both local and remote computer storage media, including memory storage devices. [0052] The order in which the method is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method, or an alternative method. Additionally, individual blocks may be deleted from the method without departing from the spirit and scope of the methods, systems and devices described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof. [0053] Referring to Fig. 4, at block 402, a user profile request may be received from a user device 104 for user profile data. The user profile request may include unique SFM information of SFM in the user device 104. In an example, the user profile request may be received by the comparison engine 210.
[0054] At block 404, a repository 108 is searched to identify information corresponding to the unique SFM information. In an example, the comparison engine 210 may query the repository 108 for information corresponding to the unique SFM information.
[0055] Further, at block 406, based on the search conducted at block 404, user profile data corresponding to the unique SFM information may be extracted. In an example, the user profile data may include personal information about the user for identification, such as name of the user, address of the user, government identification proof. In an implementation, profiling engine 212 extracts the user profile data from the repository 108.
[0056] At block 408, the user profile data extracted at block 406 may be transmitted to the user device 104. The transmission may be done by the profiling engine 212, in accordance with an implementation.
[0057] Fig. 5 illustrates an exemplary method for user profile identification using SFM information, according to an implementation of the present subject matter.

[0058] The exemplary method may be described in the general context of computer executable instructions embodied on a computer-readable medium. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, functions, etc., which perform particular functions or implement particular abstract data types. The method may also be practiced in a distributed computing environment where functions are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, computer executable instructions may be located in both local and remote computer storage media, including memory storage devices. [0059] The order in which the method is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method, or an alternative method. Additionally, individual blocks may be deleted from the method without departing from the spirit and scope of the methods, systems and devices described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof. [0060] Referring to Fig. 5, at block 502, unique SEVI information may be captured from a SEVI in a user device 104. The unique SEVI information may be present with SEVI engine 310, and may include registration number of the user device 104. In an example, the unique SEVI information may be captured by application engine 312. [0061] At block 504, a user profile request along with the unique SEVI information may be transmitted to a network entity. The user profile request may include a user profile request for user profile data of the user of the user device 104. Also, the network entity may include operator server 102. hi an example, the application engine 312 may transmit the user profile request to the network entity. [0062] Further, at block 506, in response to the user profile request sent to the network entity at block 504, user profile data may be received. In an implementation, the application engine 312 may receive the user profile data from the network entity.

[0063] Although implementations for user profile identification and automatic registration and login have been described in language specific to structural features and/or methods, it is to be understood that the present subject matter (and not appended claims) is not necessarily limited to the specific features or methods described. Rather, the specific features and methods for user profile identification and automatic registration and login are disclosed as exemplary implementations of the present invention.

I/We Claim:
1. A method for identifying user profile data, the method comprising:
receiving from a user device 104, a request for determination of the user
profile data, wherein the request comprises at least subscriber identity module (SIM)
information stored on the user device 104;
searching on a user profile database, the user profile data corresponding to the
request, based on the SIM information;
extracting the user profile data from the user profile database; and providing the extracted user profile data to the user device 104.
2. The method as claimed in claim 1, wherein the user profile data includes at least one of a name, an age, a gender, an address, a photograph, a digital signature, a location, an account balance, and a government identification proof.
3. The method as claimed in claim 1, wherein the providing the extracted user profile data to the user device 104 is performed without utilizing any user input.
4. The method as claimed in claim 3, wherein the user input comprises at least one of a login name, a login password, an email address, or other user details.
5. The method as claimed in claim 1, wherein the user profile data stored in the user profile database in a form of a look-up table.
6. The method as claimed in claim 1, wherein the SIM information includes at least an International Mobile Subscriber Identity (EVISI) number.
7. The method as claimed in claim 1, wherein the user profile data is utilized for registering a corresponding user onto an application executed on the user device 104.

8. A system for identifying user profile data, the system comprising:
a processor; and
a memory coupled to the processor, wherein the processor comprises: a comparison engine to:
receive, from a user device 104, a request for determination of the user profile data, wherein the request comprises at least subscriber identity module (SIM) information stored on the user device 104; and
search for the user profile data corresponding to the received request; and a profiling engine to:
extract the user profile data from the user profile database; and
provide the extracted user profile data to the user device 104.
9. The system as claimed in claim 8, wherein the user profile data is stored in the user profile database in a form of a look-up table.
10. The system as claimed in claim 8, wherein the SIM information includes at least an International Mobile Subscriber Identity (EVISI) number.
11. The system as claimed in claim 8, wherein the user profile data includes at least one of a name, an age, a gender, an address, a photograph, a digital signature, a location, an account balance, and a government identification proof.
12. The System as claimed in claim 8, wherein the user device 104 is at least one of a mobile phone, a tablet, and a computing terminal.

13. The system as claimed in claim 8, wherein the profiling engine provides the extracted user profile data to the user device 104 without utilizing any user input.
14. The system as claimed in claim 13, wherein the user input comprises at least one of a login name, a login password, an email address, or other user details.
15. The system as claimed in claim 8, wherein the user device 104 utilizes the user profile data for registering a corresponding user onto an application executed on the user device 104.