FIELD OF THE INVENTION:

The present invention relates to communication in a networking environment and in particular relates to management of logs related to service requests generation in the networking environment.

BACKGROUND OF THE INVENTION:

With the advent of internet to enable execution of a plethora of tasks online, various mobile devices have been developed to avail the benefits on the fly. Examples of such devices include tablets, smartphones, etc. Accordingly, accessing a mobile device application software i.e. a mobile app running on data packet network connection to access online services has surged like anything. In addition, apart from accessing data packet networks, such mobile devices are also configured to access cellular services to act as a regular mobile phone device. Accessing such dual networks through the mobile phone device facilitates the user to choose between the two networking technologies for pursuing a certain task, e.g. a phone-call may be accomplished either through cellular service or voice over internet protocol.

As a result, the mobile apps otherwise running on data packet network connection network are also not far behind and have become compatible enough to be accessed through cellular network. For example, a mobile app based on a ‘Host card emulation’ (HCE) based software architecture, i.e. a mobile wallet application, is executable on both types of networks for requesting services.

Yet, such dual-network computability based feature of the mobile apps are restricted towards meeting primary requirements, such as merely requesting a service, and don’t enable the mobile device to receive a log associated with one or more user requests in absence of the data packet connection. As a result, the mobile device is able to receive complete log information only upon resuming connection to the data packet network. This severely compromises the user experience in respect of utilizing the mobile apps, as one has to be undesirably content with receiving limited facilities due to absence of connectivity to a particular network, while the other network is absolutely functional. In absence of the log receipt during the inactive data packet network connection, the mobile device user can never ascertain the fate of the requested service and has to wait for data packets to arrive, despite the fully active state of the cellular network. Therefore, an under-utilization of resources takes place, thereby leading to an overall cost-inefficiency.

Accordingly, there is a long felt need to enable a successful sending of a complete log information to a mobile device in respect of one or more requests made by the mobile device through a network run mobile device application software (or a network run mobile app), irrespective of connectivity of said mobile device to a particular network.

Yet, another need of the hour is to enable the mobile device at receiving a complete log information regarding the services requested through one or more network-run apps, via the cellular network.

Yet another long felt need another need of the hour is to enable the mobile device at receiving a complete log information regarding the services requested through one or more network-run apps, preferentially via the data packet network, and alternatively via the cellular network in case of non-available data packet connection.

OBJECT OF THE INVENTION:

Thus, it is an object of the present invention to provide a method and system for enabling sending of a complete log information to a mobile device, in response to one or more service requests generated through a network run mobile app, via a corresponding cellular network associated with the mobile device.

It is another object of the present invention to enable a mobile device at receiving a complete log information via a cellular network, in response to service requests generated through one or more network-run mobile app.

It is another object of the present invention to enable the aforesaid sending of the complete log information and a consequent receipt of the same by the mobile device, preferentially via the data packet network, and alternatively via the cellular network in case of non-availability of the data packet connection.

SUMMARY OF THE INVENTION:

Accordingly, the present invention provides a method comprising receiving a request triggered by operation of a mobile device, creating a log for the request, and sending an SMS including the log to the mobile device such that the SMS is displayed within a particular environment inside the mobile device.

The present invention also provides a system comprising a receiver for receiving a request triggered by operation of a mobile device, a processor for creating a log for the request, and a transmitter for sending an SMS including the log to the mobile device such that the SMS is displayed within a particular environment inside the mobile device.

The present invention further provides a method comprising sending a request, receiving an SMS comprising a log created for said request; and rendering said SMS through a particular environment hosted within a mobile device.

The present invention further provides a system comprising a transmitter for sending a request, a receiving port for receiving an SMS comprising a log created for said request, and a processor for rendering said SMS through a particular environment hosted within a mobile device.
The present invention furthermore provides a method for communicating a log for a mobile-device generated request. The method comprises operating a mobile device so as to generate a request, receiving the request thus generated by the operation of the mobile device, creating a log for the received request, sending an SMS including the log to the mobile device, and rendering the SMS including the log within a particular environment inside the mobile device.
The present invention furthermore provides a system for communicating a log for a mobile-device generated request. The system comprises a mobile device for generating a request, a receiver for receiving the request thus generated by the operation of the mobile device, a processor for creating a log for the received request, a transmitter for sending an SMS including the log to the mobile device; and a particular environment hosted within said mobile device for rendering the SMS including the log.
The present invention further provides a method comprising receiving a request triggered by operation of a mobile device, creating a log for the request, and sending, depending upon a data packet receiving status of the mobile device, an SMS including the log to the mobile device such that the SMS is displayed within a particular environment inside the mobile device.

The present invention furthermore describes a system comprising a receiver for receiving a request triggered by operation of a mobile device, a processor for creating a log for the request, and a transmitter in operational interconnection with said processor for sending, depending upon a data packet receiving status of the mobile device, an SMS including the log to the mobile device such that the SMS is displayed within a particular environment inside the mobile device.
To further clarify 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 drawings. It is appreciated that these drawings depict only typical embodiments of the invention and are therefore not to be considered limiting of its scope. The invention will be described and explained with additional specificity and detail with the accompanying drawings.

BRIEF DESCRIPTION OF FIGURES:

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 shows a flow chart corresponding to a first embodiment of the invention;
Figure 2 shows a detailed internal construction of the apparatus in accordance with a first embodiment of the present invention;
Figure 3 shows a flow chart corresponding to a second embodiment of the invention;
Figure 4 shows a detailed internal construction of the apparatus in accordance with the second embodiment of the present invention;
Figure 5 shows a flow chart corresponding to a third embodiment of the invention;
Figure 6 shows a detailed internal construction of the apparatus in accordance with the third embodiment of the present invention;
Figure 7 shows a flow chart corresponding to a fourth embodiment of the invention;
Figure 8 shows a detailed internal construction of the apparatus in accordance with the fourth embodiment of the present invention;
Figure 9 shows a detailed internal construction of the apparatus as described in Fig. 2, 4, 6 and 8;
Figure 10 shows an exemplary implementation of a networking environment corresponding to application of the first till fourth embodiments of the present invention;
Figure 11 shows an exemplary control flow diagram as applicable within the implementation described in Fig. 10;
Figure 12 shows an exemplary implementation of the system in accordance with the second embodiment of the present invention; and
Figure 13 illustrates another exemplary implementation of the system in accordance with the second embodiment of the present invention.

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:

For the purpose of promoting an understanding of the principles of the invention, reference will now be made to the embodiment illustrated in the drawings and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended, such alterations and further modifications in the illustrated system, and such further applications of the principles of the invention as illustrated therein being contemplated as would normally occur to one skilled in the art to which the invention relates.
It will be understood by those skilled in the art that the foregoing general description and the following detailed description are exemplary and explanatory of the invention and are not intended to be restrictive thereof.

Reference throughout this specification to “an aspect”, “another aspect” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrase “in an embodiment”, “in another embodiment” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.

The terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such process or method. Similarly, one or more devices or sub-systems or elements or structures or components proceeded by "comprises... a" does not, without more constraints, preclude the existence of other devices or other sub-systems or other elements or other structures or other components or additional devices or additional sub-systems or additional elements or additional structures or additional components.

Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The system, methods, and examples provided herein are illustrative only and not intended to be limiting.

Embodiments of the present invention will be described below in detail with reference to the accompanying drawings.

Now referring to Figure 1, it can be seen that the present invention provides a method comprising:
receiving (step 101) a request triggered by operation of a mobile device;
creating (step 102) a log for the request; and
sending (step 103) an SMS including the log to the mobile device such that the SMS is displayed within a particular environment inside the mobile device.

In an embodiment, wherein said request comprises a request to process a token/parameter associated with a user account.

In another embodiment of the invention, wherein said request is triggered by detection of said mobile device in a pre-determined operational state by at least one of a sensing media, an NFC based detector, and a POS device.

In still another embodiment, wherein said sending of SMS comprises sending said SMS to a designated port of said mobile device to enable receipt of said SMS through said particular environment by said mobile device.

In a further embodiment of the invention, wherein said environment inside the mobile device is at least one of: an NFC card emulation application, NFC compatible application, and a HCE application

In another embodiment, wherein said environment additionally assists said detection of the mobile device during said operational state and thereafter, said triggering of the request.

Referring to Figure 2, the present invention also provides a system (200) comprising:
a receiver (201) for receiving a request triggered by operation of a mobile device;
a processor (202) for creating a log for the request; and
a transmitter (203) for sending an SMS including the log to the mobile device such that the SMS is displayed within a particular environment inside the mobile device.

Now referring to Figure 3, it can be seen that the present invention further provides a method comprising:
sending (step 301) a request;
receiving (step 302) an SMS comprising a log created for said request; and
rendering (step 303) said SMS through a particular environment hosted within a mobile device.

In an embodiment, wherein the present invention further comprises:
storing (step 304) said SMS locally within said mobile device; and
re-rendering (step 305) said stored log through said environment

Referring to Figure 4, the present invention also provides a system (400) comprising:
a transmitter (401) for sending a request;
a receiving port (402) for receiving an SMS comprising a log created for said request; and
a processor (403) for rendering said SMS through a particular environment hosted within a mobile device.

Now referring to Figure 5, it can be seen that the present invention further provides a method managing a log for a mobile-device generated request comprising:
operating (501) a mobile device so as to generate a request;
receiving (502) the request thus generated by the operation of the mobile device;
creating (503) a log for the received request;
sending (504) an SMS including the log to the mobile device; and
rendering (505) the SMS including the log within a particular environment inside the mobile device.

Referring to Figure 6, the present invention also provides a system formed by a combination of systems (200, 400) for managing a log for a mobile-device generated request, said system comprising:
a mobile device (400) for generating a request;
a receiver (201) for receiving the request thus generated by the operation of the mobile device;
a processor (202) for creating a log for the received request;
a transmitter (203) for sending an SMS including the log to the mobile device; and
said mobile device (400) hosting a particular environment for rendering the SMS including the log.

In the present embodiment described by Fig. 6, the aforesaid mobile device (400) incorporates the system (400) as described in the second embodiment of the present subject matter. Accordingly, the system (400) in a stand-alone form may be understood as an alternative to the mobile device (400) in Fig. 6.

Now referring to Figure 7, it can be seen that the present invention further provides a method comprising:
receiving (701) a request triggered by operation of a mobile device;
creating (702) a log for the request; and
sending (703), depending upon a data packet receiving status of the mobile device, an SMS including the log to the mobile device such that the SMS is displayed within a particular environment inside the mobile device.

In an embodiment, wherein the SMS is sent, in case the data packet receiving status of the mobile device is “non-active”.

In yet another embodiment, the present invention further comprises querying (704) a mobile network element about the data packet receiving status of the mobile device.

In yet another embodiment, the present invention further comprises sending (705) a data packet comprising the log to the mobile device for rendering within the particular environment inside the mobile device, in case the data packet receiving status of the mobile device is “active”.

Referring to Figure 8, the present invention also provides a system (800) comprising:
a receiver (801) for receiving a request triggered by operation of a mobile device;
a processor (802) for creating a log for the request; and
a transmitter (803) in operational interconnection with said processor (802) for sending, depending upon a data packet receiving status of the mobile device, an SMS including the log to the mobile device such that the SMS is displayed within a particular environment inside the mobile device.

Referring to figure 9, yet another typical hardware configuration of the systems 200, 400, 600, 800 in the form of a computer system 900 is shown. 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 a processor 902 e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both. The processor 902 may be a component in a variety of systems. For example, the processor 902 may be part of a standard personal computer or a workstation. The processor 902 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 analysing and processing data The processor 902 may implement a software program, such as code generated manually (i.e., programmed).

The computer system 900 may include a memory 904, such as a memory 904 that can communicate via a bus 908. The memory 904 may be a main memory, a static memory, or a dynamic memory. The memory 904 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, the memory 904 includes a cache or random access memory for the processor 902. In alternative examples, the memory 904 is separate from the processor 902, such as a cache memory of a processor, the system memory, or other memory. The memory 904 may be an external storage device or database for storing data. Examples include a hard drive, compact disc ("CD"), digital video disc ("DVD"), memory card, memory stick, floppy disc, universal serial bus ("USB") memory device, or any other device operative to store data. The memory 904 is operable to store instructions executable by the processor 902. The functions, acts or tasks illustrated in the figures or described may be performed by the programmed processor 902 executing the instructions stored in the memory 904. 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, firm-ware, 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 902, or specifically as an interface with the software stored in the memory 904 or in the drive unit 916.

Additionally, the computer system 900 may include an input device 912 configured to allow a user to interact with any of the components of system 900. The input device 912 may be a number pad, a keyboard, or a cursor control device, such as a mouse, or a joystick, touch screen display, remote control or any other device operative to interact with the computer 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 904 or within the processor 902 during execution by the computer system 900. The memory 904 and the processor 902 also may include computer-readable media as discussed above.

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 902 or may be a separate component. The communication port 920 may be created in software or may be 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 connections 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 926 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.

In an alternative example, dedicated hardware implementations, such as application specific integrated circuits, programmable logic arrays and other hardware devices, can be constructed to implement various parts of the system 900.

Applications that may include the systems can broadly include a variety of electronic and computer systems. One or more examples described may implement functions using two or more specific interconnected hardware modules or devices with related control and data signals that can be communicated between and through the modules, or as portions of an application-specific integrated circuit. Accordingly, the present system encompasses software, firmware, and hardware implementations.

The system described may be implemented by software programs executable by a computer system. Further, in a non-limited example, implementations can include distributed processing, component/object distributed processing, and parallel processing. Alternatively, virtual computer system processing can be constructed to implement various parts of the system.

The system is not limited to operation with any particular standards and protocols. For example, standards for Internet and other packet switched network transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP) may be used. Such standards are periodically superseded by faster or more efficient equivalents having essentially the same functions. Accordingly, replacement standards and protocols having the same or similar functions as those disclosed are considered equivalents thereof.
In the following paragraphs, a detailed description about exemplary implementation of the invention and a control flow within such exemplary implementation has been provided. It should however, be understood every implementation of as claimed method and apparatus need not follow the components and steps as described mentioned in the following paragraphs. Thus, the scope of the claims is intended to be restricted only on the basis of the claims and their equivalents and not on the basis of the examples provided herein below.

EXEMPLARY IMPLEMENTATION IN A NETWORKING ENVIRONMENT

Fig. 10 depicts a technical and exemplary implementation of the systems 200, 400, 600 and 800 as defined in Fig. 2, Fig. 4, Fig. 6 and Fig. 8 in a networking environment, wherein the systems are communicatively linked with each other through a network. The systems 200, 400, 600 and 800 are further connected to an authentication mechanism 1002, and a point of sale device 1004 (NFC enabled), and a mobile network element 1006 or a mobile network operator 1006 for discharging their respectively functionalities. The authentication mechanism 1002 may be a stand-alone system or a subset of the system 200, 800. In addition, the present networking environment may be implemented through a plurality of networking technologies like cellular network, data packet network, near field communication, radio frequency based networking, etc.

Various operational steps in respect of the present implementation denoted by the arrows and reference numerals 1 to 8 have been depicted within the figure 10, wherein the order of reference numerals from 1 to 8 defines a sequence of operation within the exemplary networking implementation in Fig. 10. Accordingly, these operational steps depict a combination of functionalities specific to each system (200, 400, 600, 800) in Fig. 10 by virtue of their interconnection.

The operational steps 1 to 6B have been explained in the order of their sequence with respect to Fig. 11 be for better clarity. Fig. 11 denotes a control flow diagram denoting occurrence of various events from top to bottom, thereby depicting the sequence of operational steps 1 to 6A of Fig 10 in an alternate way. Accordingly, regard may be had to a conjoined observation of Fig. 10 and Fig. 11 for understanding the steps 1 to 6A that have been illustrated as follows:

Step 1 denotes the point of sale device (POS) 1004 device sending an APDU (application protocol data unit) command to a mobile device 400. The mobile device 400 processes the command through an installed network-run mobile app, e.g. a Mobile wallet application based on the HCE architecture, to in turn request a service, say a contactless payment request. In an example, the POS device 1004 is an NFC based detector to read magnetic cards, while the mobile wallet application is one of an NFC card emulation application, NFC compatible application, and a HCE application. Specifically, to receive the APDU command, the mobile device 400 is brought within a pre-determined proximity of the POS device 1002 and a consequent detection of the mobile device 400 in a pre-determined operational state takes place. Such operational state refers to the mobile device 400 hosting the mobile wallet application. Accordingly, the mobile wallet application assists the detection of the mobile device 400.

In step 2, the mobile device 400 sends an APDU response to the POS device 1004 through the mobile wallet application. In an example, the APDU response comprises a request to process a token/parameter associated with a user account associated with the mobile wallet application. As quoted earlier, such response sending is preceded by detection of the mobile device 400 hosting the mobile wallet application and the response is generated through said application.

In step 3, the POS device 1004 constructs an authorization request and sends it to an acquirer end of a transaction system 200, 800 that corresponds to the first and fourth embodiment of the present invention. In an example, the transaction system 200, 800 may be linked with a payer bank (or any other financial institution) that is associated with the mobile wallet application and a payee bank associated with the POS device 1004. However, in other examples, the bank associated with application may also act as a payee, while the bank associated with the POS device 1004 may be a payer bank. Nevertheless, the acquirer end of the transaction system 200, 800 is linked to the bank or financial institution associated with the merchant establishment maintaining the POS device 1004

In step 4, an issuer end of the transaction system 200, 800 sends an authorization request or authentication request to a tokenization server 1002 that acts as the authentication mechanism 1002. The issuer end of the transaction system 200, 800 is associated with the bank or any other financial institution associated with the mobile wallet application.

As already aforementioned, the tokenization server 1002 may either be stand-alone or integrated with the transaction system 200, 800. Examples of the transaction system 200, 800 denote an authenticating server that receives a token from the mobile wallet application and compares it with the pre-determined criteria to authenticate a user account and accordingly permit the intended service (intended transaction) requested by user.

In step 5A, the tokenization server 1002 decodes the token from a cryptogram present within the request, compares the same with a pre-determined criteria and sends an authorization response (positive or negative) to the issuer end of the transaction system 200, 800. In an exemplary scenario, the token may be either a variable representing a 16 digit number of the magnetic card or the 16-digit number itself.

Further, as a part of Step 5A, the tokenization server 1002 prepares a log concerning the positive or negative result associated with the authentication. In case of negative result, the log may only have to comprise failure indication and at best reason behind the failure. Accordingly, the created log in such a scenario may be sent instantly, as the grant of the request has been terminated owing to authentication failure.

In other scenario, wherever the authentication is successful and further processing of the request is inevitable, the constructed log carries may carry additional details. For example, in such a scenario, the log covers further details of processing of request like date and time of executed transaction, status of transaction, value of transaction, execution of transaction, final result of transaction, user account details etc. Accordingly, the log is constructed gradually and thereafter sent upon completion of the construction

In step 5B, the created transaction log is sent in the form of the SMS from the tokenization server 1002 to the mobile network operator (MNO) 1006 that corresponds to the network of the mobile device 400. The mobile network operator 1006 may be identified based on a mobile device identifier present within the request, e.g. an MSISDN of the mobile device 400.

In case, wherever the transaction log need not carry details, especially in case of the negative authentication result as aforementioned, the transaction log under the present step 5B may be immediately sent to the MNO 1006 after its generation

However, in case of positive authentication, the sending of the created log to the MNO 1006 may not be immediate and instead happen once the requested transaction is complete e.g. the user account has been debited or credited. In addition, there may be scenarios, where the log may also record details of never completed transactions despite positive authentication, for example, due to insufficient balance, banking error, or any other reason that prevents an otherwise authenticated user account from transacting. Accordingly, in such a scenario, the present step 5B instead succeeds the forthcoming step 6A that is meant with the execution of the service (e.g. transaction) as requested by the user through the mobile device. Accordingly, the step 5B may not succeed the step 5A.

In other exemplary scenario, even in case if positive authentication, the step 5B may still precede step 6A. In such a scenario, the transaction log communication may be spread across more than one SMS to carry additional information. Accordingly, the step 5B precedes step 6A, and thereafter repeats itself in another form to also succeed the step 6A.

Further, without prejudice to the negative or positive authentication, the occurrence of step 5B may be contingent upon a data packet receiving status of the mobile device 400 that has initiated or triggered the request. The MNO 1006 or any other network element may be queried by the tokenization server 1002 or the authentication mechanism 1004 to determine the data packet receiving status of the mobile device 400. In case said data packet connection is “active”, then the log is directly communicated from the tokenization server 1002 to the mobile device 400 in the form of data packet, without being sent as an SMS through the intervention of MNO 1006.

In case the data packet connection is not “active”, then the communication of log is accomplished through SMS to the mobile device 400 via the MNO 1006.

In step 6A, the transaction system 200, 800 sends the POS device 1002 a negative or positive authentication result as determined above. Accordingly, in case of the negative result, the POS 1004 is empowered to exhibit a failure notice and terminate any further activity with respect to the concerned mobile device 400. However, in case of positive result, the POS 1004 is empowered to access the user account associated with the mobile device 400 and perform the service/transaction as requested by the mobile device 400. Example of requested services/transaction include debiting of the user account in lieu of some product or service availed by a user, crediting of user account with a certain sum, or simple updating redeeming loyalty point as accrued to the user account etc.

Further as mentioned before, in case of positive authentication result, the step 5B succeeds the step 6A either by occurring for the first time or repeating itself. Accordingly, the transaction log incorporating the details of the execution of the request is communicated to the MNO 1006 in the form of SMS either by the payment network 200, 800 or the tokenization server 1002.

In step 6B, the transaction log in the form of SMS is communicated to the mobile device 400 via the MNO 1006. The sending of SMS comprises sending said SMS to a designated port of said mobile device 400 to enable receipt of said SMS only through said particular mobile wallet application.

Now the remaining steps 7 and 8 of Fig.10 shall be explained with reference with to Fig. 10.

In step 7, the mobile device 400 through its mobile wallet app receives the SMS comprising the transaction log and stores in the same in a cyclic memory for an immediate display.

In step 8, the mobile wallet app displays the transaction log through any known format associated with mobile wallet application or any other third party application based on the HCE architecture. In an example, the transaction status may be automatically displayed as a flash message, a notification, a pop up window, or any other format to attract user attention. Irrespective of its viewed status by the mobile device user, the transaction log subsequently gets stored within a permanent memory of the mobile device 400 or a cloud based memory associated the with mobile wallet application for later access.

Further, forthcoming figures describe an exemplary implementation of the mobile device 400 or the system 400 described in the second embodiment, for enabling a user in accessing the stored transaction logs.

Figure 12 shows an exemplary implementation of the system 400 in accordance with the second embodiment of the present invention. The operational steps may be referred by the reference numerals 1 to 4, and accordingly the order of numerals defines the sequence of these operational steps. Specifically, such operational steps cumulatively point to a scenario where the user wishes to access the transaction log as automatically stored within the mobile device 400 through the mobile wallet application.

In step 1, user requests the mobile wallet application 1202 within the mobile device 400 to view the transaction log through a mobile device display unit 1204.

In step 2, the mobile wallet application 1202 requests a storage 1206 for the desired transaction log. The storage 1206 may be a permanent memory of the mobile device 400 or a cloud based memory associated with the mobile wallet application 1202.

In step 3, the transaction log storage 1206 responds back with the desired transaction log.

In step 4, the mobile wallet application 1202 displays the transaction log at the mobile device display unit 1204.

Another exemplary implementation of the mobile device 400 for accessing stored transaction logs from the mobile wallet app 1202 has been depicted in Fig 13, wherein a password or PIN based authentication may be introduced as a security check to enable access of the stored transaction log by the authorized user. The operational steps may be referred by the reference numerals 1 to 7, and accordingly the order of numerals define the sequence of these operational steps

In step 1, user requests the application 1202 to view the transaction log at the mobile device display unit 1204.

In step 2, the mobile wallet app 1202 prompts the user for authentication (Wallet PIN).

In step 3, the mobile wallet app 1202 receives the Authentication data (Wallet PIN) from user.

In step 4, the mobile wallet app 1202 authenticates 1202 user by verifying the Authentication data (Wallet PIN). If authentication has failed, mobile wallet app 1202 aborts the process and displays the appropriate message to the user. If authentication has been met, the mobile wallet app 1202 proceeds to step 5.

In step 5, the mobile wallet app 1202 requests the transaction log storage 1206 for the desired Transaction log.

In step 6, the transaction log storage 1206 responds back with the desired transaction log.

In step 7, the mobile wallet app 1202 displays the transaction log at the mobile device’s display unit 1204.

By virtue of the embodiments and implementations described so far, the present invention enables communication of the log related to usage of a network connection run mobile app, say an HCE based mobile app, to the mobile device 400 and receipt of the same without being bothered about any internet connection or mobile data connection. As a result, even the POS device 1004 need not be specifically actuated to enable the aforesaid communication and the receipt.

Overall, the present invention uses an existing infrastructure i.e. cellular network that is reliable and inexpensive for log communication and accordingly does not require the mobile device 400 to sync up with server at regular intervals merely for the purposes of procuring the transaction logs. Accordingly, the user experience is enhanced as alerts about a request success or failure and other ancillary details are communicated irrespective of the connectivity to the data packet network, thereby leading to efficient network utilization.

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.

CLAIMS:We Claim:
1. A method comprising:
receiving (101) a request triggered by operation of a mobile device;
creating (102) a log for the request; and
sending (103) an SMS including the log to the mobile device such that the SMS is displayed within a particular environment inside the mobile device.

2. The method as claimed in claim 1, wherein said request comprises a request to process a token/parameter associated with a user account.
3. The method as claimed in claim 1, wherein said request is triggered by detection of said mobile device in a pre-determined operational state by at least one of a sensing media, an NFC based detector, and a POS device.
4. The method as claimed in claim 1, wherein said sending of SMS comprises sending said SMS to a designated port of said mobile device to enable receipt of said SMS through said particular environment by said mobile device.
5. The method as claimed in claim 1, wherein said environment inside the mobile device is at least one of: an NFC card emulation application, NFC compatible application, and a HCE application
6. The method as claimed in claim 1, wherein said environment additionally assists said detection of the mobile device during said operational state and thereafter, said triggering of the request.
7. A system (200) comprising:
a receiver (201) for receiving a request triggered by operation of a mobile device;
a processor (202) for creating a log for the request; and
a transmitter (203) for sending an SMS including the log to the mobile device such that the SMS is displayed within a particular environment inside the mobile device.

8. A method comprising:
sending (301) a request;
receiving (302) an SMS comprising a log created for said request; and
rendering (303) said SMS through a particular environment hosted within a mobile device.

9. The method as claimed in claim 10, further comprising:
storing (304) said SMS locally within said mobile device; and
re-rendering (305) said stored log through said environment.

10. A system (400) comprising:
a transmitter (401) for sending a request;
a receiving port (402) for receiving an SMS comprising a log created for said request; and
a processor (403) for rendering said SMS through a particular environment hosted within a mobile device.

11. A method for communicating a log for a mobile-device generated request, said method comprising:
operating (501) a mobile device so as to generate a request;
receiving (502) the request thus generated by the operation of the mobile device;
creating (503) a log for the received request;
sending (504) an SMS including the log to the mobile device; and
rendering (505) the SMS including the log within a particular environment inside the mobile device.

12. A system (200, 400) for communicating a log for a mobile-device generated request, said system comprising:
a mobile device (400) for generating a request;
a receiver (201) for receiving the request thus generated by the operation of the mobile device;
a processor (202) for creating a log for the received request;
a transmitter (203) for sending an SMS including the log to the mobile device; and
said mobile device (400) hosting a particular environment for rendering the SMS including the log.

13. A method comprising:
receiving (701) a request triggered by operation of a mobile device;
creating (702) a log for the request; and
sending (703), depending upon a data packet receiving status of the mobile device, an SMS including the log to the mobile device such that the SMS is displayed within a particular environment inside the mobile device.

14. The method as claimed in claim 10, wherein the SMS is sent, in case the data packet receiving status of the mobile device is “non-active”.
15. The method as claimed in claim 10, further comprising querying (704) a mobile network element about the data packet receiving status of the mobile device.
16. The method as claimed in claim 10, wherein in case the data packet receiving status of the mobile device is “active”, the method further comprises sending (705) a data packet comprising the log to the mobile device for rendering within the particular environment inside the mobile device.
17. A system (800) comprising:
a receiver (801) for receiving a request triggered by operation of a mobile device;
a processor (802) for creating a log for the request; and
a transmitter (803) in operational interconnection with said processor (802) for sending, depending upon a data packet receiving status of the mobile device, an SMS including the log to the mobile device such that the SMS is displayed within a particular environment inside the mobile device.