FIELD OF THE INVENTION
The present disclosure relates to telecommunication and in particular, relates to a systems and methods for obtaining Mobile Station Integrated Services Digital Network (MSISDN) of a User Equipment when subscribing to a service.
BACKGROUND
With the advent of cellular technology, users have become more and more dependent on services provided by a cellular network providers or an operator. It is often that the operators may be the service provider or may engage a third-party service provider. The users are further required to pay for the services initiated/availed to the service provider.
The regulatory authorities have implied several regulatory steps to ensure the user provides an explicit consent for availing the services provided by the operator. For this reason, operators may have to place steps for receiving the user consent for initiating any service. A part of such regulation may be to obtain a Mobile Station Integrated Services Digital Network (MSISDN).
Usually, while subscribing to a service, it is relevant to ensure that the operator takes on-record consent from the user. In a known technique the MSISDN may be obtained in a Hypertext Transfer Protocol (HTTP) header while requesting for subscription of the service from a user equipment (UE). Sometimes, the MSISDN, i.e., the user's mobile number may not appear in HTTP header as consent.
Owing to this absence of MSISDN in the HTTP header, the operator may have to bear economical loss, for example, due to a consequent reduction in a number of subscriptions. In order to avoid this, the operator may have to request the user to share the MSISDN separately.
In such cases, the user may provide the MSISDN or the mobile number to the operator after multiple clicks and further authentication using the UE, such as entering One-Time Password (OTP). Now, receiving the OTP further poses another concern, for instance, the UE may be in a poor network zone and may not be able to receive the OTP. Therefore, the user then may have to wait for the OTP as well.
Therefore, there exist a need to create a system and method which may ease to obtain the MSISDN from the UE for initiating the service.

SUMMARY
This summary is provided to introduce a selection of concepts in a simplified format that are further described in the detailed description of the invention. This summary is not intended to identify key or essential inventive concepts of the invention, nor is it intended for determining the scope of the invention.
In an implementation, the present subject matter refers to a method for obtaining a Mobile Station Integrated Services Digital Network (MSISDN) by a server for initiating a service. The method includes establishing a communication with a User Equipment (UE) based on a first request received from the UE. The method includes providing a request page and a token corresponding to the request page to the UE upon establishing communication, wherein the request page is indicative of submitting a second request for initiating the service. The method includes receiving the second request and the token from the UE based on submission of the request page for initiating the service; and obtaining the MSISDN associated with the UE through at least one of a call, a text message, an Unstructured Supplementary Service Data (USSD) string and an application based on the received second request and the corresponding token for initiating the service.
In an implementation, the present subject matter refers to a system for obtaining a Mobile Station Integrated Services Digital Network (MSISDN) for initiating a service. The system includes a server in communication a user equipment (UE) including a memory storing instructions; and a processor configured to execute the instructions to perform operations to: establish a communication with the UE based on a first request received from the UE; provide a request page and a token corresponding to the request page to the UE upon establishing communication, wherein the request page is indicative of submitting a second request for initiating the service; receive the second request and the token from the UE based on submission of the request page for initiating the service; and obtain the MSISDN associated with the UE through at least one of a call, a text message, an Unstructured Supplementary Service Data (USSD) string and an application based on the received second request and the corresponding token for initiating the service.
To further clarify the advantages and features of the present invention, a more particular description of the invention will be rendered by reference to specific embodiments thereof, which is illustrated in the appended drawing. It is appreciated that these drawings depict only typical embodiments of the invention and are therefore not to be considered limiting its scope. The

invention will be described and explained with additional specificity and detail with the accompanying drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
These and other features, aspects, and advantages of the present invention will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:
Figure 1 illustrates a block diagram depicting an environment of implementation of the present invention, according to an embodiment of the present disclosure;
Figure 2 illustrates a flowchart for obtaining a Mobile Station Integrated Services Digital Network (MSISDN) by a server for initiating a service, in accordance with an embodiment of the present disclosure;
Figure 3 illustrates an example implementation flowchart for obtaining the MSISDN associated with the UE through a call, in accordance with an embodiment of the present disclosure;
Figure 4 illustrates an example implementation flowchart for obtaining the MSISDN associated with the UE through a text message, in accordance with an embodiment of the present disclosure;
Figure 5 illustrates an example implementation flowchart for obtaining the MSISDN associated with the UE through an Unstructured Supplementary Service Data (USSD) string, in accordance with an embodiment of the present disclosure;
Figure 6 illustrates an example implementation flowchart for obtaining the MSISDN associated with the UE through a application, in accordance with an embodiment of the present disclosure;
Figure 7 illustrates an example implementation flowchart for obtaining the MSISDN associated with the UE through one-time password, in accordance with an embodiment of the present disclosure;
Figure 8 illustrates a system architecture in accordance with an embodiment of the present disclosure; and
Figure 9 illustrates another system architecture, in accordance with an embodiment of the present disclosure.

Further, skilled artisans will appreciate that elements in the drawings are illustrated for simplicity and may not have been necessarily been drawn to scale. For example, the flow charts illustrate the method in terms of the most prominent steps involved to help to improve understanding of aspects of the present invention. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having benefit of the description herein.
DETAILED DESCRIPTION
It should be understood at the outset that although illustrative implementations of the embodiments of the present disclosure are illustrated below, the present invention may be implemented using any number of techniques, whether currently known or in existence. The present disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary design and implementation illustrated and described herein, but may be modified within the scope of the appended claims along with their full scope of equivalents.
The term "some" as used herein is defined as "none, or one, or more than one, or all." Accordingly, the terms "none," "one," "more than one," "more than one, but not all" or "all" would all fall under the definition of "some." The term "some embodiments" may refer to no embodiments or to one embodiment or to several embodiments or to all embodiments. Accordingly, the term "some embodiments" is defined as meaning "no embodiment, or one embodiment, or more than one embodiment, or all embodiments."
The terminology and structure employed herein is for describing, teaching and illuminating some embodiments and their specific features and elements and does not limit, restrict or reduce the spirit and scope of the claims or their equivalents.
More specifically, any terms used herein such as but not limited to "includes," "comprises," "has," "consists," and grammatical variants thereof do NOT specify an exact limitation or restriction and certainly do NOT exclude the possible addition of one or more features or elements, unless otherwise stated, and furthermore must NOT be taken to exclude the possible

removal of one or more of the listed features and elements, unless otherwise stated with the limiting language "MUST comprise" or "NEEDS TO include."
Whether or not a certain feature or element was limited to being used only once, either way it may still be referred to as "one or more features" or "one or more elements" or "at least one feature" or "at least one element." Furthermore, the use of the terms "one or more" or "at least one" feature or element do NOT preclude there being none of that feature or element, unless otherwise specified by limiting language such as "there NEEDS to be one or more ..." or "one or more element is REQUIRED."
Unless otherwise defined, all terms, and especially any technical and/or scientific terms, used herein may be taken to have the same meaning as commonly understood by one having an ordinary skill in the art.
The present invention discloses a system and method for obtaining a Mobile Station Integrated Services Digital Network (MSISDN) by a server from a User Equipment (UE) for initiating a service. In particular, the server obtains the MSISDN associated with the UE through at least one of a call, a text message, an Unstructured Supplementary Service Data (USSD) string and an application installed on the UE. Upon obtaining the MSISDN, the server initiates subscription of the service.
Embodiments of the present invention will be described below in detail with reference to the accompanying drawings.
Figure 1 illustrates a block diagram depicting an environment 100 of implementation of the present invention for obtaining MSISDN of the UE, according to an embodiment of the present disclosure.
Referring to Figure 1, the present invention may be implemented between the UE 102 and a server 106.
In an embodiment, the UE 102 may include a subscriber identity module (SIM) with unique MSISDN 104. The UE 102 may include, but is not limited to, a tablet PC, a Personal Digital Assistant (PDA), a mobile-device, a palmtop computer, a cellular mobile, a communications device, a wireless-telephone, or any other machine controllable through the wireless-network and capable of executing a set of instructions (sequential or otherwise) that

specify actions to be taken by that machine. In an example, the UE 102 may be capable of communication with the server 106 may be via cellular connections, wireless connections.
In an embodiment, the server 106 may be adapted to provide the services to the UE 102. In an example, the services may be subscription to newsletter, songs, caller tunes, any other feed to be received by the UE 102. In the example, the UE 102 may have to request the server 106 to provide subscription to one or more services. The server 106 upon receiving the request from the UE 102 may request the UE 102 to provide a second consent for initiating the subscription of services and thus obtain the MSISDN 104.
In an example, the server 106 may reside with an operator providing cellular communication network to the UE 102. In another example, the server 106 may reside with a third-party content service provider in communication with the operator. In the example, the UE 102 may communicate with the operator and the operator may redirect the request for initiating the subscription of service to the server 106 at the third-party service provider. In the example, the third-party service providers may be newsfeed aggregators, songs aggregators, and alike. In the example, the server 106 and the UE 102 may act as the client-server architecture. The implementation details of obtaining the MSISDN 104 by the server 106 from the UE 102 for initiating the service shall be discussed in detail in the forthcoming paragraphs.
Figure 2 illustrates a flowchart for obtaining the MSISDN 104 by the server 106 for initiating the service, in accordance with an embodiment of the present disclosure.
As depicted in Figure 2, the present subject matter refers to a method 200 for obtaining the MSISDN 104 by the server 106 from the UE 102.
The method 200 may be a computer-implemented method executed, for example, by the UE 102 and the server 106. For the sake of brevity, constructional and operational features are explained in the description of Figure 8, and Figure 9.
At step 202, the method 200 may include establishing communication between the UE 102 and the server 106. In an embodiment, the UE 102 may be adapted to send a first request to the server 106 wherein the first request is corresponding to initiate subscription to the service. In an example, the UE 102 establishes wireless communication with the server 106 and selects the service out of one or more services being provided by the server 106. The server 106 upon receiving request from the UE 102 may validate if the UE 102 is eligible for availing said services.

In the example, the UE 102 may already be in active communication with the server 106 if the server 106 resides at the operator premises. In the example, the UE 102 may be redirected by the operator for establishing communication if the server 106 resides at the third-part site.
At step 204, the method 200 may include the server 106 upon receiving the request from the UE 102, providing a request page and a token to the UE 102. In an embodiment, the UE 102 receives the request page and the token from the server 106 for further processing. In an example, the request page is indicative of submitting a second request by the UE 102 to the server 106 for initiating the services. In the example, the request page is displayed on the UE 102. The notification may include OK/SUBMIT button for providing second request to the server 106. The notification may also include message indicating that the server 106 is requesting the second request in form of the request page from the UE 102 for initiating the services. In an example, the token is a unique private key embedded in the request page, provided by the server 106 to the UE 102. In the example, the token is generated by the server 106 upon receiving the first request from the UE 102 for initiating the services.
At step 206, the method 200 may include the server 106 receiving the second request and the token from the UE based on submission of the request page for initiating the service. The second request received by the server 106, upon the UE 102 submitting the request page indicates the UE 102 consent to initiate the services. In an embodiment, the server 106 validates the token received with the second request. In an example, the server 106 matches the token received with the second request and the token provided with the request page. In the example, the server 106 is adapted to recognize and validate that the UE 102 submitting the second request and the UE 102 receiving the request page from the server 106 are identical if the token matches.
At step 208, the method 200 may include the server 106 obtaining the MSISDN 104. In an embodiment the server 106 obtains the MSISDN from the UE 102 through at least one of the call, the text message, the USSD string and the application installed on the UE 102. In an example, the UE 102 may be adapted to select the call, the text message, the USSD string or the application to provide MSISDN 104 to the server 106.
Figure 3 illustrates an example implementation flow 300 for obtaining the MSISDN 104 associated with the UE 102 through the call, in accordance with an embodiment of the present disclosure.

At step 302, the method 300 may include the server 106 receiving an application programming interface (API) request. In an embodiment, the API request is initiated simultaneously by the UE 102 upon submitting the request page. In an example, the server 106 may be adapted to determine through the API request that the UE 102 may prefer to provide the MSISDN 104 through the call.
At step 304, the method 300 may include initiating the call by the UE 102 to a communication platform. In an embodiment, a dialler may be opened on the UE 102 to initiating the call to the communication platform. In an example, the dialler may be pre-filled with a toll-free number using which the UE 102 initiates the call to the communication platform.
In an embodiment, the communication platform receives the MSISDN 104 associated with the UE upon receiving the call and the token associating the MSISDN 104 with the second request for initiating the service. In an example, the communication platform may or may not reside in the server 106. In the example, the communication platform may provide the UE 102 ability to remote access the server 106 and exchange files and messages in text, calls, audio and/or video formats. In an embodiment, the communication platform upon receiving the call from the UE 102 also receives the MSISDN 104 associated with said UE 102. In an example, the communication platform may receive the token along with the MSISDN.
At step 306, the method 300 may include obtaining the MSISDN 104 associated with the UE 102 from the communication platform. In an example, the communication platform may transmit the MSISDN 104, and the token received from the UE 102 to the server 106.
At step 308, the method 300 may include validating the token to confirm the second request. In an example, the server 106 may be adapted to validate the token along with the second request received. In the example, the server 106 stores the MSISDN 104 associated with the UE 102. Further, as the second request and token are validated, the server 106 is adapted to initiate the services as requested by the UE 102.
At step 310, the method 300 may include the server 106 sending a message to the UE 102. In an example, the message may include notifying the UE 102 about the successful initiation of the services.

Figure 4 illustrates an example implementation flowchart for obtaining the MSISDN 104 associated with the UE 102 through the text message, in accordance with an embodiment of the present disclosure.
At step 402, the method 400 may include the server 106 receiving the API request. In an embodiment, the API request is initiated simultaneously by the UE 102 upon submitting the request page. In an example, the server 106 may be adapted to determine through the API request that the UE 102 may prefer to provide the MSISDN 104 through the text message.
At step 404, the method 400 may include the server 106 providing the text message to the UE 102. In an example, the server 106 upon receiving the submitted request page as the second request may provide the text message to the UE 102.
At step 406, the method 400 may include the server 106 receiving the text message by the UE 102 on the communication platform. In an embodiment, a text messenger may be opened on the UE 102. In an example, the text messenger may be pre-filled with the text message using which the UE 102 initiates the text message to the communication platform.
In an embodiment, the communication platform receives the MSISDN 104 associated with the UE upon receiving the text message and the token associating the MSISDN 104 with the second request for initiating the service. In an embodiment, the communication platform upon receiving the text message from the UE 102 also receives the MSISDN 104 associated with said UE 102. In an example, the communication platform may receive the token along with the MSISDN.
At step 408, the method 400 may include obtaining the MSISDN 104 associated with the UE 102 from the communication platform. In an example, the communication platform may transmit the MSISDN 104 and the token received from the UE 102 to the server 106.
At step 410, the method 400 may include validating the token to confirm the second request. In an example, the server 106 may be adapted to validate the token along with the second request received. In the example, the server 106 stores the MSISDN 104 associated with the UE 102. Further, as the second request and token are validated, the server 106 is adapted to initiate the services as requested by the UE 102.

At step 412, the method 400 may include the server 106 sending the message to the UE 102. In an example, the message may include notifying the UE 102 about the successful initiation of the services.
Figure 5 illustrates an example implementation flowchart for obtaining the MSISDN 104 associated with the UE 102 through the USSD string, in accordance with an embodiment of the present disclosure.
At step 502, the method 500 may include the server 106 receiving the API request. In an embodiment, the API request is initiated simultaneously by the UE 102 upon submitting the request page. In an example, the server 106 may be adapted to determine through the API request that the UE 102 may prefer to provide the MSISDN 104 through the text message.
At step 504, the method 500 may include the server 106 providing the USSD string to the UE 102. In an example, the server 106 upon receiving the submitted request page as the second request may provide the USSD string to the UE 102.
At step 506, the method 500 may include the initiating the USSD string to be received by the communication platform. In an embodiment, the dialler may be opened on the UE 102. In an example, the dialler may be pre-filled with the USSD string using which the UE 102 initiates the USSD request to the communication platform.
In an embodiment, the communication platform receives the MSISDN 104 associated with the UE upon receiving the USSD string request and the token associating the MSISDN 104 with the second request for initiating the service. In an embodiment, the communication platform upon receiving the USSD string request from the UE 102 also receives the MSISDN 104 associated with said UE 102. In an example, the communication platform may receive the token along with the MSISDN.
At step 508, the method 500 may include obtaining the MSISDN 104 associated with the UE 102 from the communication platform. In an example, the communication platform may transmit the MSISDN 104 and the token received from the UE 102 to the server 106.
At step 510, the method 500 may include validating the token to confirm the second request. In an example, the server 106 may be adapted to validate the token along with the second

request received. In the example, the server 106 stores the MSISDN 104 associated with the UE 102. Further, as the second request and token are validated, the server 106 is adapted to initiate the services as requested by the UE 102.
At step 512, the method 500 may include the server 106 sending the message to the UE 102. In an example, the message may include notifying the UE 102 about the successful initiation of the services.
Figure 6 illustrates an example implementation flowchart for obtaining the MSISDN 104 associated with the UE 102 through the application, in accordance with an embodiment of the present disclosure.
At step 602, the method 600 may include the server 106 receiving the API request. In an embodiment, the API request is initiated simultaneously by the UE 102 upon submitting the request page. In the method 600, the API request may be initiated via the operator or wireless communication such as Wi-Fi. In an example, the server 106 may be adapted to determine through the API request that the UE 102 may prefer to provide the MSISDN 104 through the application. In an embodiment, the application may be pre-installed in the UE 102.
At step 604, the method 600 may include initiating the application installed in the UE 102. In an embodiment, the application may be initiated to send the second request, token and the MSISDN associated with the UE 102 to the server 106.
At step 606, the method 600 may include obtaining the MSISDN 104 associated with the UE 102 through the application. In an example, the application may transmit the MSISDN 104 and the token received from the UE 102 to the server 106.
At step 608, the method 600 may include validating the token to confirm the second request. In an example, the server 106 may be adapted to validate the token along with the second request received. In the example, the server 106 stores the MSISDN 104 associated with the UE 102. Further, as the second request and token are validated, the server 106 is adapted to initiate the services as requested by the UE 102.

At step 610, the method 600 may include the server 106 sending a message to the UE 102. In an example, the message may include notifying the UE 102 about the successful initiation of the services.
Figure 7 illustrates an example implementation flowchart for obtaining the MSISDN 104 associated with the UE 102 through one-time password, in accordance with an embodiment of the present disclosure.
At step 702, the method 700 may include the server 106 sending an information page to the UE 102. In an embodiment, the server 106 may provide the information page to the UE 102 upon failure to receive second request from UE 102 in a stipulated interval of time. In an example, the information page is indicative of requesting the UE 102 to submit MSISDN 104 and a one¬time password (OTP) corresponding to initiating the service. In an example, the server 106 post receiving the first request from the UE 102 and providing the request page may wait for the stipulated interval of time.
In an alternate embodiment, the server 106 may provide the information page to the UE 102 even upon failure to receive the second request from the UE through any one of the call, the text message, the Unstructured Supplementary Service Data (USSD) string and the application.
At step 704, the method 700 may include the sever 106 to provide the OTP to the UE 102. In an example, the OTP may include a numerical string which may be used as private key token to establish identity and may act as password for initiating the service.
At step 706, the method 700 may include the server 106 receiving the information page submitted by the UE 102.
At step 708, the method 700 may include the server 106 obtaining the MSISDN 104 associated with the UE through the submitted information page for initiating the service.
Figure 8 illustrates a representative architecture 800 to provide tools and implementation environment described herein for a technical realization of a system 802 for obtaining the MSISDN 104 through interaction of the UE 102 and the server 106. Figure 8 is merely a non-limiting example, and it will be appreciated that many other architectures may be implemented to

facilitate the functionality described herein. The architecture 800 may be executing on hardware such as the UE 102 and the server 106 of Fig. 8 that includes, among other things, processors, memory, and various application-specific hardware components.
The architecture 800 may include an operating-system, libraries, frameworks or middleware. The operating system may manage hardware resources and provide common services. The operating system may include, for example, a kernel, services, and drivers defining a hardware interface layer. The drivers may be responsible for controlling or interfacing with the underlying hardware. For instance, the drivers may include display drivers, camera drivers, Bluetooth® drivers, flash memory drivers, serial communication drivers (e.g., Universal Serial Bus (USB) drivers), Wi-Fi® drivers, audio drivers, power management drivers, and so forth depending on the hardware configuration.
A hardware interface layer includes libraries which may include system libraries such as filesystem (e.g., C standard library) that may provide functions such as memory allocation functions, string manipulation functions, mathematic functions, and the like. In addition, the libraries may include API libraries such as audio-visual media libraries (e.g., multimedia data libraries to support presentation and manipulation of various media format such as MPEG4, H.264, MP3, AAC, AMR, JPG, PNG), database libraries (e.g., SQLite that may provide various relational database functions), web libraries (e.g., WebKit that may provide web browsing functionality), and the like.
A middleware may provide a higher-level common infrastructure such as various graphic user interface (GUI) functions, high-level resource management, high-level location services, and so forth. The middleware may provide a broad spectrum of other APIs that may be utilized by the applications or other software components/modules, some of which may be specific to a particular operating system or platform.
The term "module" used in this disclosure may refer to a certain unit that includes one of hardware, software and firmware or any combination thereof. The module may be interchangeably used with unit, logic, logical block, component, or circuit, for example. The module may be the minimum unit, or part thereof, which performs one or more particular functions. The module may be formed mechanically or electronically. For example, the module disclosed herein may include

at least one of ASIC (Application-Specific Integrated Circuit) chip, FPGAs (Field-Programmable Gate Arrays), and programmable-logic device, which have been known or are to be developed.
Further, the architecture 800 includes the system 802 implemented in the server 106 and the UE 102. The server 106 may include the communication platform 804 in communication with the UE 102. The server 106 may include the processor 806 in communication with the communication platform 804 and operatively coupled with a memory 808. The processor 806 is configured to obtain the MSISDN 104 from the UE 102.
In an embodiment, the system 802 for obtaining the MSISDN 104 from the UE 102 by the server 106 is disclosed, according to an embodiment of the present disclosure. For the sake of brevity, the system 802 for obtaining the MSISDN 104 from the UE 102 by the server 106 is hereinafter interchangeably referred to as the system 802.
In an embodiment, the server 106 is configured to establish a communication with the UE 102 based on the first request received from the UE 102.
Further, the server 106 is configured to provide the request page and the token corresponding to the request page to the UE 102 upon establishing communication. In an example, the request page is indicative of submitting a second request for initiating the service.
In an embodiment, the server 106 receive the second request and the token from the UE 102 based on submission of the request page for initiating the service.
In an embodiment the server 106 obtains the MSISDN 104 associated with the UE 102 through at least one of a call, a text message, an Unstructured Supplementary Service Data (USSD) string and an application based on the received second request and the corresponding token for initiating the service.
In an embodiment, the processor 806 is configured to obtain the MSISDN 104 associated with the UE 102 through the call. In an example, the processor 806 receive the API request upon receiving the second request and the token from the UE 102. In the example, the processor 806 is configured to provide the calling number to the UE based on submission of the request page. The processor 806 is configured to initiate the call by the UE to the communication platform 804. In the example the communication platform 804 receives the MSISDN 104 associated with the UE

102 and the token associating the MSISDN 104 with the second request for initiating the service. The processor 806 is configured to obtain the MSISDN associated with the UE 102 from the communication platform 804 upon the UE 102 initiating the call. In the example, the processor 806 is configured to validate the second request and the MSISDN 104 for initiating the service. In the example, the processor 806 is configured to initiate the service and send the message to UE 102 indicating successful initiation of the service.
In an embodiment, the processor 806 is configured to obtain the MSISDN 104 associated with the UE 102 through the USSD string. In an example, the processor 806 is configured to receive the API request upon receiving the second request and the token from the UE 102. Further, processor 806 is configured to provide the USSD string to the UE 102 based on submission of the request page. In the example, the processor 806 is configured to initiate the USSD string by the UE 102 to the communication platform, wherein the communication platform receives the MSISDN associated with the UE 102 and the token associating the MSISDN with the second request for initiating the service. In the example, the processor 806 is configured to obtain the MSISDN associated with the UE 102 from the communication platform 804 upon the UE 102 initiating the USSD string and validate the second request and the MSISDN for initiating the service. In the example, the processor 806 is configured to initiate the service and send the message to UE 102 indicating successful initiation of the service.
In an embodiment, the processor 806 is configured to obtain the MSISDN 104 associated with the UE 102 through the message. In an example, the processor 806 is configured to receive the API request upon receiving the second request and the token from the UE 102. Further, the processor 806 is configured to provide the message to the UE 102 based on submission of the request page. In the example, the processor 806 is configured to receive the message by the UE 102 on the communication platform 804. In the example, the communication platform 804 receives the MSISDN 104 associated with the UE 102 and the token associating the MSISDN 104 with the second request for initiating the service. The processor 806 is configured to obtain the MSISDN 104 associated with the UE 102 from the communication platform 804 upon the UE 102 receiving the message and validate the second request and the MSISDN 104 for initiating the service.
In an embodiment, the processor 806 is configured to obtain the MSISDN 104 associated with the UE 102 through the application. In an example, the processor 806 is configured to receive

the API request upon receiving the second request and the token from the UE. Further, the processor 806 is configured to initiate the application installed in the UE. In the example, the processor 806 is configured to obtain the MSISDN 104 associated with the UE from the application as the application is initiated or triggered. The processor 806 is configured to validate the second request and the MSISDN 104 for initiating the service.
In an embodiment, the processor 806 is configured to obtain the MSISDN 104 associated with the UE 102 through a one-time password (OTP). In an example, the processor 806 is configured to provide an information page upon failure to receive the second request from the UE 102. In the example, the information page is indicative of requesting the UE 102 to submit MSISDN 104 and the OTP corresponding to initiating the service. In the example, the processor 806 is configured to provide the OTP to the UE 102. The processor 806 is configured to receive the information page submitted by the UE 102 and obtain the MSISDN 104 associated with the UE 102 through the information page for initiating the service.
Figure 9 illustrates another system architecture of the system 802 in the form of a computer system 900. The computer system 900 can include a set of instructions that can be executed to cause the computer system 900 to perform any one or more of the methods disclosed. The computer system 900 may operate as a standalone device or may be connected, e.g., using a network, to other computer systems or peripheral devices.
In a networked deployment, the computer system 900 may operate in the capacity of a server or as a client user computer in a server-client user network environment, or as a peer computer system in a peer-to-peer (or distributed) network environment. The computer system 900 can also be implemented as or incorporated across various devices, such as a personal computer (PC), a tablet PC, a personal digital assistant (PDA), a mobile device, a palmtop computer, a laptop computer, a desktop computer, a communications device, a wireless telephone, a land-line telephone, a web appliance, a network router, switch or bridge, or any other machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while a single computer system 900 is illustrated, the term "system" shall also be taken to include any collection of systems or sub-systems that individually or jointly execute a set, or multiple sets, of instructions to perform one or more computer functions.

The computer system 900 may include the processor 806 e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both. The processor 406 may be a component in a variety of systems. For example, the processor 406 may be part of a standard personal computer or a workstation. The processor 806 may be one or more general processors, digital signal processors, application-specific integrated circuits, field-programmable gate arrays, servers, networks, digital circuits, analog circuits, combinations thereof, or other now known or later developed devices for analyzing and processing data. The processor 806 may implement a software program, such as code generated manually (i.e., programmed).
The computer system 900 may include a memory 808, such as a memory 808 that can communicate via a bus 908. The memory 808 may include but is not limited to computer-readable storage media such as various types of volatile and non-volatile storage media, including but not limited to random access memory, read-only memory, programmable read-only memory, electrically programmable read-only memory, electrically erasable read-only memory, flash memory, magnetic tape or disk, optical media and the like. In one example, memory 808 includes a cache or random-access memory for the processor 806. In alternative examples, the memory 808 is separate from the processor 806, such as a cache memory of a processor, the system memory, or other memory. The memory 808 may be an external storage device or database for storing data. The memory 808 is operable to store instructions executable by the processor 806. The functions, acts or tasks illustrated in the figures or described may be performed by the programmed processor 806 for executing the instructions stored in the memory 808. The functions, acts or tasks are independent of the particular type of instructions set, storage media, processor or processing strategy and may be performed by software, hardware, integrated circuits, firmware, micro-code and the like, operating alone or in combination. Likewise, processing strategies may include multiprocessing, multitasking, parallel processing and the like.
As shown, the computer system 900 may or may not further include a display unit 910, such as a liquid crystal display (LCD), an organic light-emitting diode (OLED), a flat panel display, a solid-state display, a cathode ray tube (CRT), a projector, a printer or other now known or later developed display device for outputting determined information. The display 910 may act as an interface for the user to see the functioning of the processor 806, or specifically as an interface with the software stored in the memory 808 or the drive unit 916.

Additionally, the computer system 900 may include an input device 912 configured to allow the user to interact with any of the components of system 900. The computer system 900 may also include a disk or optical drive unit 916. The disk drive unit 916 may include a computer-readable medium 922 in which one or more sets of instructions 924, e.g., software, can be embedded. Further, the instructions 924 may embody one or more of the methods or logic as described. In a particular example, the instructions 924 may reside completely, or at least partially, within the memory 808 or within the processor 806 during execution by the computer system 900.
The present invention contemplates a computer-readable medium that includes instructions 924 or receives and executes instructions 924 responsive to a propagated signal so that a device connected to a network 926 can communicate voice, video, audio, images, or any other data over the network 926. Further, the instructions 924 may be transmitted or received over the network 926 via a communication port or interface 920 or using a bus 908. The communication port or interface 920 may be a part of the processor 806 or maybe a separate component. The communication port 920 may be created in software or maybe a physical connection in hardware. The communication port 920 may be configured to connect with a network 926, external media, the display 910, or any other components in system 900, or combinations thereof. The connection with the network 926 may be a physical connection, such as a wired Ethernet connection or may be established wirelessly as discussed later. Likewise, the additional connections with other components of the system 900 may be physical or may be established wirelessly. The network 926 may alternatively be directly connected to the bus 908.
The network 926 may include wired networks, wireless networks, Ethernet AVB networks, or combinations thereof. The wireless network may be a cellular telephone network, an 802.11, 802.16, 802.20, 802.1Q or WiMax network. Further, the network 5526 may be a public network, such as the Internet, a private network, such as an intranet, or combinations thereof, and may utilize a variety of networking protocols now available or later developed including, but not limited to TCP/IP based networking protocols. The system is not limited to operation with any particular standards and protocols. For example, standards for Internet and other packet-switched network transmissions (e.g., TCP/IP, UDP/IP, HTML, and HTTP) may be used.
While specific language has been used to describe the disclosure, any limitations arising on account of the same are not intended. As would be apparent to a person in the art, various

working modifications may be made to the method in order to implement the inventive concept as taught herein.
The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein.
Moreover, the actions of any flow diagram need not be implemented in the order shown; nor do all of the acts necessarily need to be performed. Also, those acts that are not dependent on other acts may be performed in parallel with the other acts. The scope of embodiments is by no means limited by these specific examples. Numerous variations, whether explicitly given in the specification or not, such as differences in structure, dimension, and use of material, are possible. The scope of embodiments is at least as broad as given by the following claims.
Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any component(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential feature or component of any or all the claims.
The present invention provides following advantages:
1. The operator may have a much reliable process to obtain the MSISDN of the UE.
2. The present invention streamlines the process to receive the second consent in form of second request.
3. The present invention provides multiple options to the obtain the MSISDN.
4. The present invention provides an automated solution to obtain the MSISDN without the user making multiple clicks and providing manual information.
5. The present invention reduced the number of clicks for user while handling the service,
thus making the process more efficient.
6. The present invention provides a simple, reliable process to obtain MSISDN which may
be working even in low or poor network.

WE CLAIM:

1. A method for obtaining a Mobile Station Integrated Services Digital Network (MSISDN)
by a server for initiating a service, the method comprising:
establishing a communication with a User Equipment (UE) based on a first request received from the UE;
providing a request page and a token corresponding to the request page to the UE upon establishing communication, wherein the request page is indicative of submitting a second request for initiating the service;
receiving the second request and the token from the UE based on submission of the request page for initiating the service; and
obtaining the MSISDN associated with the UE through at least one of a call, a text message, an Unstructured Supplementary Service Data (USSD) string and an application based on the received second request and the corresponding token for initiating the service.
2. The method as claimed in claim 1, wherein the method further comprises:
providing an information page upon failure to receive the second request from the UE, wherein the information page is indicative of requesting the UE to submit MSISDN and a one-time password (OTP) corresponding to initiating the service;
providing the OTP to the UE;
receiving the information page submitted by the UE;
obtaining the MSISDN associated with the UE through the information page for initiating the service.
3. The method as claimed in claim 1, wherein obtaining the MSISDN associated with the
UE through the call comprises:
receiving an application programming interface (API) request upon receiving the second request and the token from the UE;
providing a calling number to the UE based on submission of the request page;

initiating the call by the UE to a communication platform, wherein the communication platform receives the MSISDN associated with the UE and the token associating the MSISDN with the second request for initiating the service;
obtaining the MSISDN associated with the UE from the communication platform upon the UE initiating the call; and
validating the second request and the MSISDN for initiating the service.
4. The method as claimed in claim 3, wherein the method further comprises:
sending a message to the UE indicating successful initiation of the service.
5. The method as claimed in claim 1, wherein obtaining the MSISDN associated with the
UE through the USSD string comprises:
receiving the API request upon receiving the second request and the token from theUE;
providing the USSD string to the UE based on submission of the request page;
initiating the USSD string by the UE to the communication platform, wherein the communication platform receives the MSISDN associated with the UE and the token associating the MSISDN with the second request for initiating the service;
obtaining the MSISDN associated with the UE from the communication platform upon the UE initiating the USSD string; and
validating the second request and the MSISDN for initiating the service.
6. The method as claimed in claim 5, wherein the method further comprises:
sending a message to the UE indicating successful initiation of the service.
7. The method as claimed in claim 1, wherein obtaining the MSISDN associated with the
UE through the message comprises:
receiving the API request upon receiving the second request and the token from theUE;
providing the message to the UE based on submission of the request page;

receiving the message by the UE on the communication platform, wherein the communication platform receives the MSISDN associated with the UE and the token associating the MSISDN with the second request for initiating the service;
obtaining the MSISDN associated with the UE from the communication platform upon the UE sending the message; and
validating the second request and the MSISDN for initiating the service.
8. The method as claimed in claim 7, wherein the method further comprises:
sending a message to the UE indicating successful initiation of the service.
9. The method as claimed in claim 1, wherein obtaining the MSISDN associated with the
UE through the application comprises:
receiving the API request upon receiving the second request and the token from theUE;
initiating the application installed in the UE;
obtaining the MSISDN associated with the UE from the application upon the application initiated; and
validating the second request and the MSISDN for initiating the service.
10. The method as claimed in claim 9, wherein the method further comprises:
sending a message to the UE indicating successful initiation of the service.
11. The method as claimed in claim 9, wherein the server is one of a content provider server.
12. The method as claimed in any of the preceding claims, wherein obtaining the MSISDN associated with the UE further comprises:
receiving the API request upon receiving the second request and the token from theUE;
attempting to obtain the MSISDN associated with the UE through any one of the call, the text message, the Unstructured Supplementary Service Data (USSD) string and the application;
providing the information page upon failure to receive the second request from the UE through any one of the call, the text message, the Unstructured Supplementary

Service Data (USSD) string and the application, wherein the information page is indicative of requesting the UE to submit MSISDN and a one-time password (OTP) corresponding to initiating the service;
providing the OTP to the UE;
receiving the information page submitted by the UE;
obtaining the MSISDN associated with the UE through the information page for initiating the service.
13. A method for sending a Mobile Station Integrated Services Digital Network (MSISDN)
by a UE for initiating a service, the method comprising:
establishing a communication with a server based on a first request sent by the UE;
receiving a request page and a token corresponding to the request page from the server upon establishing communication, wherein the request page is indicative of submitting a second request for initiating the service;
sending the second request and the token to the server based on submission of the request page for initiating the service; and
sending the MSISDN associated with the UE through at least one of a call, an Unstructured Supplementary Service Data (USSD) string, a text message and an application based on the sent second request and the corresponding token for initiating the service.
14. The method as claimed in claim 13, wherein the method further comprises:
receiving an information page upon failure to send the second request to the server, wherein the information page is indicative of submitting the MSISDN and a one-time password (OTP) corresponding to initiating the service;
receiving the OTP from the server;
sending the information page to the server;

sending the MSISDN associated with the UE through the information page for initiating the service.
15. The method as claimed in claim 13, wherein sending the MSISDN associated with the
UE through the call comprises:
sending an application programming interface (API) request upon sending the second request and the token to the server;
receiving a calling number from the server based on submission of the request page;
initiating the call to a communication platform, wherein the communication platform receives the MSISDN associated with the UE and the token associating the MSISDN with the second request for initiating the service.
16. The method as claimed in claim 15, wherein the method further comprises:
receiving a message from the server indicating successful initiation of the service.
17. The method as claimed in claim 13, wherein sending the MSISDN associated with the
UE through the USSD string comprises:
sending the API request upon sending the second request and the token to the server;
receiving the USSD string from the server based on submission of the request page;
initiating the USSD string connecting to the communication platform, wherein the communication platform receives the MSISDN associated with the UE and the token associating the MSISDN with the second request for initiating the service.
18. The method as claimed in claim 17, wherein the method further comprises:
receiving a message from the server indicating successful initiation of the service.
19. The method as claimed in claim 13, wherein sending the MSISDN associated with the
UE through the message comprises:

sending the API request upon sending the second request and the token from the UE;
receiving the message from the server based on submission of the request page;
sending the message to connect with the communication platform, wherein the communication platform receives the MSISDN associated with the UE and the token associating the MSISDN with the second request for initiating the service.
20. The method as claimed in claim 19, wherein the method further comprises:
receiving a message from the server indicating successful initiation of the service.
21. The method as claimed in claim 13, wherein sending the MSISDN associated with the
UE through the application comprises:
sending the API request upon sending the second request and the token from the UE;
initiating the application installed in the UE;
sending the MSISDN associated with the UE through the application.
22. The method as claimed in claim 21, wherein the method further comprises:
receiving a message from the server indicating successful initiation of the service.
23. The method as claimed in claim 13, wherein the server is one of a content provider server.
24. A system for obtaining a Mobile Station Integrated Services Digital Network (MSISDN) for initiating a service, the system comprising:
a server in communication a user equipment (UE) comprises:
a memory storing instructions; and
a processor configured to execute the instructions to perform operations

establish a communication with the UE based on a first request received from the UE;
provide a request page and a token corresponding to the request page to the UE upon establishing communication, wherein the request page is indicative of submitting a second request for initiating the service;
receive the second request and the token from the UE based on submission of the request page for initiating the service; and
obtain the MSISDN associated with the UE through at least one of a call, a text message, an Unstructured Supplementary Service Data (USSD) string and an application based on the received second request and the corresponding token for initiating the service.
25. The system as claimed in claim 24, wherein the processor is further configured to:
provide an information page upon failure to receive the second request from the UE, wherein the information page is indicative of requesting the UE to submit MSISDN and a one-time password (OTP) corresponding to initiating the service;
provide the OTP to the UE;
receive the information page submitted by the UE;
obtain the MSISDN associated with the UE through the information page for initiating the service.
26. The system as claimed in claim 24, wherein the processor is configured to obtain the
MSISDN associated with the UE through the call, further configured to:
receive an application programming interface (API) request upon receiving the second request and the token from the UE;
provide a calling number to the UE based on submission of the request page;
initiate the call by the UE to a communication platform, wherein the communication platform receives the MSISDN associated with the UE and the token associating the MSISDN with the second request for initiating the service;

obtain the MSISDN associated with the UE from the communication platform upon the UE initiating the call; and
validate the second request and the MSISDN for initiating the service.
27. The system as claimed in claim 26, wherein the processor further configured to:
send a message to the UE indicating successful initiation of the service.
28. The system as claimed in claim 24, wherein the processor is configured to obtain the
MSISDN associated with the UE through the USSD string, the processor further
configured to:
receive the API request upon receiving the second request and the token from the UE;
provide the USSD string to the UE based on submission of the request page;
initiate the USSD string by the UE to the communication platform, wherein the communication platform receives the MSISDN associated with the UE and the token associating the MSISDN with the second request for initiating the service;
obtain the MSISDN associated with the UE from the communication platform upon the UE initiating the USSD string; and
validate the second request and the MSISDN for initiating the service.
29. The system as claimed in claim 28, wherein the processor further configured to:
send a message to the UE indicating successful initiation of the service.
30. The system as claimed in claim 24, wherein the processor is configured to obtain the
MSISDN associated with the UE through the message, the processor further configured
to:
receive the API request upon receiving the second request and the token from the UE;
provide the message to the UE based on submission of the request page;
receive the message by the UE on the communication platform, wherein the communication platform receives the MSISDN associated with the UE and the token associating the MSISDN with the second request for initiating the service;

obtain the MSISDN associated with the UE from the communication platform upon the UE receiving the message; and
validate the second request and the MSISDN for initiating the service.
31. The system as claimed in claim 30, wherein the processor further configured to:
send a message to the UE indicating successful initiation of the service.
32. The system as claimed in claim 24, wherein the processor is configured to obtain the
MSISDN associated with the UE through the application, the processor further
configured to:
receive the API request upon receiving the second request and the token from the UE;
initiate the application installed in the UE;
obtain the MSISDN associated with the UE from the application upon the application initiated; and
validate the second request and the MSISDN for initiating the service.
33. The system as claimed in claim 32, wherein the processor further configured to:
send a message to the UE indicating successful initiation of the service.
34. The system as claimed in claim 24, wherein the server is one of a content provider server.