WO2012131686A1

WO2012131686A1 - Configuration driven application persona on hand held terminals

Info

Publication number: WO2012131686A1
Application number: PCT/IN2011/000227
Authority: WO
Inventors: Subbakrishna Ramesh KIRAN KANNAMBADI; Gautam Bandyopadhyay
Original assignee: Infosys Technologies Limited
Priority date: 2011-03-31
Filing date: 2011-03-31
Publication date: 2012-10-04
Also published as: AP2013007207A0

Abstract

[0038] The present disclosure relates to configuration driven application persona on hand held terminals. The system comprises a data receiving unit configured to receive a memory unit and also to read the data present in the memory unit. The data receiving unit can also be initialized using the memory unit. The data authenticating unit coupled to the data receiving unit is configured to receive at least one input from the memory unit and at least one second input from the user to verify the data present in the memory unit. The data processing unit coupled with the data receiving unit processes the at least one input from the memory unit and at least one second input from the user to selectively display the features on an output display. The configuration unit is communicably coupled with the memory unit wherein the configuration unit can be used to update the memory unit.

Description

Configuration driven application persona on hand held terminals

Technical Field

[0001] The present disclosure relates to software updating techniques and personalized software provisioning techniques. The present disclosure provides a system and a method for Configuration driven application persona on hand held.

Background

[0002] The point of sale terminals/ hand held terminals are currently loaded with specialized applications which have a specific set of features. These features are coded and the binaries are deployed on the hand-held terminal. The main limitation with the existing technologies is the upgrade process. Typically the upgrade of the application to introduce new features is associated with a development cycle for the required enhancements. The development lifecycle introduces a delay and also increases the cost of the enhancement.

[0003] In addition, the logistics issues involved in distributing the application are quite high. The fact that there could be multiple versions of applications deployed in the field will bring in the complexity of backward compatibility of the server side infrastructure.

[0004] Further, there are practical instances when software present- on the device needs to be updated. The technologies present in the art involve updating the software present on the hand held device itself. These methods are often tedious, not cost efficient and not secure. There are also instances when certain users are given different rights or permissions to use single software on a single point of sales terminal or device. The technology to solve this kind of a problem is not present in the art. Hence there is a need to technology that provides facility for this problem.

Summary

[0005] Aspects of the disclosure relate to a method and a system to a configuration driven application persona on hand held terminals. The invention addresses the problem of having a specific application for each deployment and the related issues of time to market, cost of application distribution and application version compatibility.

l [0006] It does so by providing a process of developing a set of business components which can be linked together in a specific manner to achieve the required feature. The manner of linking is in itself defined externally on a smart card which is used at the time of starting up the device.

[0007] The persona of the device/ the feature set available on the device is now dependent on the following:

a. The smart card used to power-up the device - thus providing not just a device specific persona but a device user specific persona b. The device user specific persona adds to the security by providing a different set of features based on user rights.

[0008] The smart card which powers up the device can be updated easily at multiple locations both through the hand held terminal or externally.

[0009] According to the present disclosure, the system comprises a data receiving unit a data authenticating unit, a data processing unit and an updating module. The data receiving unit is configured to receive a memory unit which can be a smart card. The data receiving unit can be any hand held device, for example a hand held point of sales terminal. The memory unit can also be used to start up or initiate the data receiving unit.

[0010] The data authenticating unit which is coupled to the data receiving unit can authenticate the data present in the memory unit. The data present in the memory unit comprises a user related data of that particular memory unit and also other information. The data authenticating unit can receive an input from the user to authenticate the data present in the memory unit.

[0011] The data processing unit which is coupled to the data receiving unit processes the data present in the memory unit based on the inputs. The data processing unit also can display the persona on an output device, which can be an output screen of a hand held device. The configuring unit can be used to update the memory unit. Detailed Description of the Drawings

[0012] Fig. 1 is a block diagram of an exemplary embodiment illustrating a system for configuration driven application persona on hand held terminals of the present disclosure.

[0013] Fig. 2 is a block diagram of an exemplary embodiment illustrating a method for configuration driven application persona on hand held terminals of the present disclosure.

[0014] FIG. 3 is a system illustrating a generalized computer network arrangement, in one embodiment of the present technique.

Detailed Description of an Exemplary Embodiment

[0015] The present disclosure proposes a system for configuration driven application persona on hand held terminals. Fig. 1 is a block diagram of an exemplary embodiment illustrating a system for configuration driven application persona on hand held terminals of the present disclosure. The block diagram indicates a system 100 which comprises a data receiving unit 110, a memory unit 120, a data authenticating unit 130, a data processing unit 150, an updating module 160, an output device 170 and a configuring unit 180.

[0016] The data receiving unit 110 is configured to receive a memory unit 120. The data receiving unit can be a hand held device at a point of sales terminal or any device deployed at a sales terminal. The memory unit can be a smart card. The memory unit 120 can assist the data receiving unit to start up or to boot. The data receiving unit 110 once started can read the contents from the memory unit 120. The data receiving unit 110 can also be configured to start up without the memory unit 120. The data receiving unit 110 can also be configured to read at least one input from the memory unit 120. The at least one input can be. a user related, data present in the memory unit 120. The user related data comprises information about an owner of the memory unit 120. For example, the smart card, which is a memory unit 120, can contain - information of a store manager and the related rights assigned. The related rights would comprise certain rights exclusively defined for the manager such as, declining invalid transactions, or correcting transactions that has an error in it etc. [0017] The data authenticating unit 130 is coupled with the data receiving unit 110. The data authenticating unit 130 authenticates the data present in the memory unit 120 by using standard authenticating protocols such as a hand shake protocol along with the at least one second input from the user 140. The at least one second input can be a personal identification number or a password or a biometric input from the user 140.

[0018] The data processing unit 150 is coupled to the data receiving unit. The data processing unit 150 is configured to receive the at least one input from the data authenticating unit 130 and the at least one second input from the user 140 to process the input. Once the inputs are processed, based on the privileges set on the memory unit 120 the persona is displayed on the output device 170. The output device 170 can be a hand held device, or a PC, or a Kiosk or a display on point of sales. For example, if a manager is allocated a memory unit 120 which can be a smart card, corresponding rights and also other relevant data is updated on the smart card. Once the data receiving unit 110, in this case a point of sales terminal, receives the smart card, it requests the authentication for the information present in the smart card through a password etc.

[0019] Once the user 140 authenticates, the data is processed using, the data processing module 150 to process user related data present in the memory unit 120 and the output is displayed on the output device 170 based on the processed information. The data processing unit 150 allocates different set of features to different users 140 based on the user related data.

[0020] The configuration unit 180 is coupled with the memory unit 120. The memory unit 120 can be updated by updating the configuration unit using at least one database. The at least one database can be remotely located across multiple locations. The configuration unit 180 can also be further configured to assist the receiving^' unit 110 to start up. The memory unit 120 by virtue of its connection with the receiving unit 110 will upgrade the application residing on the receiving unit 110 with the new version of the application.

[0021] In another embodiment, the present disclosure describes- a - method" ft>r' eonfiguration driven application persona on hand held terminals of the present disclosure. Fig. 2 is a flow diagram of an exemplary embodiment illustrating a method for configuration driven application persona on hand held terminals of the present disclosure. Block 200 represents the steps involved in configuration driven application persona on hand held terminals. The method includes the step, 210, of receiving a specific data from a memory unit on to a receiving unit. The memory unit here can be but not restricted to a smart card. The specific data can be the user specific data present on the smart card. The user specific data can relate to the different attributes of the user such as name, employee number, privileges or rights assigned to that corresponding user etc. The receiving unit can be a point of sales terminal deployed at a point of sales. The memory unit once received at the receiving unit can assist the receiving unit to start-up. The receiving unit can also be configured to start up without the memory unit. After the receiving unit has started, then data receiving unit can receive the memory unit for further processing.

[0022] The step of authenticating the data is described in block 220. Once the memory unit is received at the receiving unit, the data in the memory unit is read by the receiving unit. A part of the data in the receiving unit corresponds to user specific data. The user specific data and other data present in the memory unit are read by the receiving unit. After reading the data from the memory unit, the next step involves authenticating the data present in the memory unit and the receiving unit. The authenticating process starts with; requesting the user to enter a password or a. personal identification number or a biometric input. This input provided by the user is further authenticated with the receiving unit by using standard protocols. A hand shake protocol can also be one of the standard authenticating protocols.

[0023] Block 230 describes the step of processing specific data and the user inputs. The specific data is processed to check the relevant rights assigned to that particular memory unit. Based on the rights in the memory unit personalized features are displayed selectively on an output device of the receiving unit. For example, if a manager inserts his smart, card at the..re,ceiving unit, after, processing the relevant information on his smart card, a set of features is displayed on the output device of the receiving unit. On the other hand, if another employee^" who is not a manger 'inserts his smart card on to the receiving unit a different set of features is displayed on the output device based on his rights. The different rights can be but not limited to-decHnmg- a transaetion-when there is an error, correcting the parameters of the transaction when there is an error in the entry etc. [0024] Block 240 corresponds to updating the memory unit. The memory unit can be updated across multiple locations remotely. The memory unit can be updated by updating the configuration data present as a part of the data residing in the memory unit. Once to memory unit is updated the data receiving can also be updated simply by coupling the memory unit with the receiving unit.

[0025] The embodiment of the disclosure can be further explained considering an example. Consider a user 140 who is a manager of a store. The user 140 receives a memory unit 120 which can be a smart card. While assigning the memory unit 140 a set of permissions are assigned to the manager on the smart card. The data receiving unit 110 receives the memory unit 120. This step of receiving the memory unit 120 by the data receiving unit 110 is also explained in the block 210 of fig.2. The memory unit 120 may also assist the data receiving unit 110 to start up. For better explanation of the example embodiment, a point of sales terminal can be the data receiving unit 110.

[0026] The data authenticating unit 130 requests the user 140 to enter an input in form of a password. The data authenticating unit 130 requests the user 140 to enter an input to authenticate the user specific data which is being read from the memory unit 120 by the data receiving unit 110. This step of authenticating the data is also described in step 220 of fig.2.

[0027] The data processing unit 150 receives user specific data from the memory unit 120 and also the password entered by the user 140. The data processing unit 150 reads the rights assigned to that particular the memory unit 120 which is present in the user specific data. Based on this information the data processing unit 150 selectively displays, the -features..on, the data .receiving., unit 110 which here is a point of sales terminal for the manager- user 140 to use the point of sales terminal. This step of processing the data is also described in the step 230 offig.2-.

[0028] Further, if the features which are being displayed: have- to be updated - tcrthenext version- or if the user specific data present on the memory unit 120 has to be updated, it can be done through multiple databases which are present across locations and it can be done remotely. The data present in the configuration unit 180 has to be changed in order to update the memory unit 140. This step of updating the memory unit is also described in the step 240 of fig.2.

[0029] One or more of the above-described techniques may be implemented in or involve one or more computer systems. Figure 3 illustrates a generalized example of a computing environment 300. The computing environment 300 is not intended to suggest any limitation as to scope of use or functionality of described embodiments.

[0030] With reference to Figure 3, the computing environment 300 includes at least one processing unit 310 and memory 320. In Figure 3, this most basic configuration 330 is included within a dashed line. The processing unit 310 executes computer-executable instructions and may be a real or a virtual processor. In a multi-processing system, multiple processing units execute computer-executable instructions to increase processing power. The memory 320 may be volatile memory (e.g., registers, cache, RAM), non-volatile memory (e.g., ROM, EEPROM, flash memory, etc.), or some combination of the two. In some embodiments, the memory 320 stores software 380 implementing described techniques.

[0031] A computing environment may have additional features. For example, the computing environment 300 includes storage 340, one or more input devices 350, one or more - output devices 360, and one or more communication connections 370. An interconnection mechanism (not shown) such as a bus, controller, or network interconnects the components of the computing environment 300. Typically, operating system software (not shown) provides an operating environment for other software executing in the computing environment 300, and^* coordinates activities of the components of the computing environment 300.

[0032] The storage 340 may be removable or non-removable, and includes magnetic disks, magnetic tapes or cassettes, CD-ROMs, CD-RWs, DVDs, or any other medium which may be used to store information and which may be accessed within the computing environment 300. In some embodiments, the storage 340 stores instructions for the software 380. [0033] The input device(s) 350 may be a touch input device such as a keyboard, mouse, pen, trackball, touch screen, or game controller, a voice input device, a scanning device, a digital camera, or another device that provides input to the computing environment 300. The output device(s) 360 may be a display, printer, speaker, or another device that provides output from the computing environment 300.

[0034] The communication connection(s) 370 enable communication over a communication medium to another computing entity. The communication medium conveys information such as computer-executable instructions, audio or video information, or other data in a modulated data signal. A modulated data signal is a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media include wired or wireless techniques implemented with an electrical, optical, RF, infrared, acoustic, or other carrier.

[0035] Implementations may be described in the general context of computer-readable media. Computer-readable media are any available media that may be accessed within a computing environment. By way of example, and not limitation, within the computing environment 300, computer-readable media include memory 320, storage 340, communication media, and combinations of any of the above.

[0036] Having described and illustrated the principles of our invention with reference to described embodiments, it will be recognized that the described embodiments may be modified in arrangement and detail without departing from such principles. It should be understood^" that the programs, processes, or methods described herein are not related or limited to any particular type of computing environment, unless indicated otherwise. Various types of general purpose or specialized computing environments may be used with or perform operations in accordance with the teachings described herein. Elements of the described embodiments shown in software may be implemented in hardware and vice versa. [0037] In view of the many possible embodiments to which the principles of our invention may be applied, we claim as our invention all such embodiments as may come within the scope and spirit of the following claims and equivalents thereto.

Claims

Claims What is claimed is

1. A system comprising:

a data receiving unit configured to receive at least one input from a memory unit and to read the memory unit, the memory unit is operable to start up the data receiving unit;

a data authenticating unit coupled with the data receiving unit, the data authenticating unit configured to authenticate the at least one input, further the data authenticating unit is operable to receive at least one second input from a user to authenticate the at least one input; a data processing unit coupled with the data receiving unit, the data processing unit configured to receive the at least one input, the data processing unit processes the at least one input, further the data processing unit selectively displays an output based on processed at least one input on an output device; and

a configuration unit communicably coupled to the memory unit, wherein the configuration unit updates the memory unit.

2. The system of claim 1 wherein the memory unit is a smart card.

3. The system of claim 1 wherein the at least one input is a user related data present in the memory unit.

4. The system of claim 1 wherein the data receiving unit is a point of sales terminal deployed at a point of sales.

5. The system of claim 1 wherein the data authenticating unit initiates a hand-shake protocol that authenticates the user related data between the memory unit and the data receiving unit.

6. The system of claim 1 wherein the data processing unit is further configured to allocate a different set of features to the user based on the user related data.

7. The system of claim 1 further comprising an updating module coupled with the data receiving unit, the updating module is configured to update the data receiving unit from at least one database remotely across multiple locations.

8. The system of claim 1 wherein the configuration unit updates the memory unit from the at least one database remotely across multiple locations.

9. The system of claim 1 wherein the data processing unit is further configured to allocate a different set of features to the user based on the user related data.

10. The system of claim 8 wherein the configuration unit is further configured to assist in starting up the data receiving unit.

11. A method comprising: receiving a specific data available in a memory unit at a receiving unit, the memory unit further assisting in starting up the receiving unit;

authenticating the memory unit and the receiving unit, the authenticating step further comprising accepting at least one input from a user at the receiving unit;

processing the specific data and the receiving unit , the processing step further comprises displaying selectively the processed specific data on an output device of the receiving unit; and

updating the memory unit with at least one database.

12. The method of claim 11, wherein the memory unit is a smart card device.

13. The method of claim 11, wherein the data receiving unit is a point of sales terminal unit deployed at a point of sales.

14. The method of claim 11 wherein the specific data i . a . user- specific, .data-present in. the,, memory unit.

15. The method of claim 11 wherein the step of starting up the receiving unit with the memory unit further comprising, initializing the receiving unit without the memory unit and coupling the memory unit with the receiving unit after the receiving unit is initialized.

16. The method of claim 11 wherein the step of authenticating the memory unit and the receiving unit further comprises, retrieving the user specific data from the memory unit and authenticating the user specific data.

17. The method of claim 11 wherein the step of authenticating the user specific data comprises using standard authentication protocols,

18. The method of claim 17 wherein the standard authentication protocols is a hand-shake protocol.

19. The method of claim 11 wherein the step of updating the memory unit comprises, updating a configuration data.

20. The method of claim 19 wherein the step of updating a configuration data further comprises, updating the configuration data remotely across multiple locations.

21. A computer program product comprising a computer usable medium having a computer readable program code embodied therein for performing a configuration driven persona on a device, the method comprising: program code adapted for receiving a specific data available in a memory unit at a receiving unit, the memory unit further assisting in starting up the receiving unit;

program code adapted for authenticating the memory unit and the receiving unit, the authenticating step further comprising accepting at least one input from a user at the receiving unit;

program code adapted for processing the specific data and the receiving unit , the processing step further comprises displaying selectively the processed specific data on an output device of the receiving unit; and program code adapted for updating the memory unit with at least one database.

22. The product of claim 21, further comprising, program code adapted for initializing the receiving unit without the memory unit and coupling the memory unit with the receiving unit after the receiving unit is initialized.

23. The product of claim 21 , further comprising program code adapted for retrieving the user specific data from the memory unit and authenticating the user specific data.

24. The product of claim 21, further comprising program code adapted for updating a configuration data

25. The product of claim 24, further comprising program code adapted for updating the configuration data remotely across multiple locations.