WO2018229673A1

WO2018229673A1 - User commitment behaviour based dynamic reputation management system and method thereof

Info

Publication number: WO2018229673A1
Application number: PCT/IB2018/054304
Authority: WO
Inventors: Naynesh PASARI
Original assignee: Pasari Naynesh
Priority date: 2017-06-15
Filing date: 2018-06-13
Publication date: 2018-12-20

Abstract

An aspect of the present disclosure provides a system for dynamically managing reputation of at least one user, said system including an offer generation engine to enable an entity to generate an offer for one or more users, wherein the offer includes one or more defined actions, an offer acceptance engine to enable at least one user to accept the offer, a commitment behaviour assessment engine to assess behaviour of the at least one user towards the one or more defined actions for determining whether the accepted offer is complied by the at least one user, and a commitment behaviour based reputation score management engine to computes a reputation score of the at least one user based on the assessment of the behaviour of the at least one user towards the one or more defined actions.

Description

USER COMMITMENT BEHAVIOUR BASED DYNAMIC REPUTATION MANAGEMENT

SYSTEM AND METHOD THEREOF

TECHNICAL FIELD

[0001] The present disclosure relates to a reputation management system, and more particularly relates to systems and methods that dynamically and in real-time manage and update reputation of one or more users based on their commitment behaviour for defined action(s).

BACKGROUND

[0002] The background description includes information that may be useful in understanding the present invention. It is not an admission that any of the information provided herein is prior art or relevant to the presently claimed invention, or that any publication specifically or implicitly referenced is prior art.

[0003] In an era of highly competitive business market, employees of an organization play a vital role in its growth. Employees enhance value of the organization by providing requisite labour and essential expertise. Thus, principal challenge of a potential recruiter is to choose suitable and creditworthy employees to ensure constant progress of the organization.

[0004] One of the traditional methods used for recruitment is by using referral recruitment strategy that encourages employees or even external contributors to refer contacts for specific positions in an organization. However, using referral recruitment strategy does not give a fair chance to numerous other prospective candidates. Consequently, the organization may lose to recruit better candidates who have failed to apply for specific positions because of referral recruitment.

[0005] Also, currently there exists no solution that provides an organization with the details of the employees regarding his probable reputation that may be based on the commitment and fulfilment of joining the organization or previous workplaces. This probable reputation may aid the recruiter to take an informed decision while recruiting an employee based on his commitment behaviour.

[0006] There is therefore a need in the art for a system that dynamically and in real-time manages and updates reputation of users that can be potential employees based on their commitment behaviour which would be beneficial to the prospective employers and organizations. [0007] All publications herein are incorporated by reference to the same extent as if each individual publication or patent application were specifically and individually indicated to be incorporated by reference. Where a definition or use of a term in an incorporated reference is inconsistent or contrary to the definition of that term provided herein, the definition of that term provided herein applies and the definition of that term in the reference does not apply.

[0008] As used in the description herein and throughout the claims that follow, the meaning of

"a," "an," and "the" includes plural reference unless the context clearly dictates otherwise. Also, as used in the description herein, the meaning of "in" includes "in" and "on" unless the context clearly dictates otherwise.

[0009] The recitation of ranges of values herein is merely intended to serve as a shorthand method of referring individually to each separate value falling within the range. Unless otherwise indicated herein, each individual value is incorporated into the specification as if it were individually recited herein. All methods described herein can be performed in any suitable order unless otherwise indicated herein or otherwise clearly contradicted by context. The use of any and all examples, or exemplary language (e.g. "such as") provided with respect to certain embodiments herein is intended merely to better illuminate the invention and does not pose a limitation on the scope of the invention otherwise claimed. No language in the specification should be construed as indicating any non-claimed element essential to the practice of the invention.

OBJECTS OF THE PRESENT DISCLOSURE

[00010] Some of the objects of the present disclosure, which at least one embodiment herein satisfies are as listed herein below.

[00011] It is an object of the present disclosure to provide systems and methods that analyse commitment behaviour of one or more users with an entity.

[00012] It is another object of the present disclosure to provide systems and methods that manage reputation of one or more users based on their commitment behaviour.

[00013] It is another object of the present disclosure to provide systems and methods to compute reputation score of the user to determine creditworthiness of the user. SUMMARY

[00014] The present disclosure relates to relates to systems and methods that dynamically and in real-time manage and update reputation of one or more users based on their commitment behaviour for defined action(s).

[00015] An aspect of the present disclosure provides a system for dynamically managing reputation of at least one user, said system comprising: a non-transitory storage device having embodied therein one or more routines operable to dynamically manage reputation of the at least one user; and one or more processors coupled to the non-transitory storage device and operable to execute the one or more routines, wherein the one or more routines include: an offer generation engine, which when executed by the one or more processors, enables an entity to generate an offer for one or more users by analysing plurality of discussions between the one or more users and the entity, wherein the offer includes one or more defined actions; an offer acceptance engine, which when executed by the one or more processors, in response to a communication received from the at least one user selected from the one or more users, enables the at least one user to accept the offer, wherein on acceptance of the offer, the at least one user confirms to perform the one or more defined actions; a commitment behaviour assessment engine, which when executed by the one or more processors, assesses behaviour of the at least one user towards the one or more defined actions to determine whether the accepted offer is complied by the at least one user; and a commitment behaviour based reputation score management engine, which when executed by the one or more processors, computes a reputation score of the at least one user based on the assessment of the behaviour of the at least one user towards the one or more defined actions.

[00016] In an embodiment, the system further comprises a registration engine, which when executed by the one or more processors, enables any or a combination of the entity or the one or more users to register with the system, and further verify and authorize each registered user and the registered entity.

[00017] In an embodiment, the registration engine registers the one or more users based on user details provided by respective one or more users and wherein each user is verified and authorized based on a unique identifier associated with said user.

[00018] In an embodiment, the registration engine performs verification and authorization of each user by conducting a background check of user details provided by each user. [00019] In an embodiment, the one or more defined actions comprises any or a combination of reporting to the entity on a specified joining date, attending premises of the entity for a pre-defined duration, tasks to be performed in a pre-defied duration, maintaining confidentiality while performing tasks, serving a notice period on deciding to dissociate with the entity or any other terms, which the entity requires the one or more user to perform.

[00020] In an embodiment, the entity is any of an organization, a land owner, a supplier of goods or a service provider, which require the one or more users to perform the one or more defined actions.

[00021] In an embodiment, the commitment behaviour assessment engine assesses behaviour of the at least one user towards the one or more defined actions for a pre-defined duration.

[00022] In an embodiment, the reputation score of the at least one user is increased when the accepted offer is complied by the at least one user and the reputation score of the at least one user is decreased when the accepted offer is not-complied by the at least one user.

[00023] In an embodiment, the commitment behaviour based reputation score management engine computes a reputation score of the entity based on attributes of the entity comprising any or a combination of employees working for the entity, working capital of the entity, infrastructure of the entity, customer service provided by the entity, intellectual capital of the entity and financial performance of the entity.

[00024] Another aspect of the present disclosure provides a method for dynamically managing reputation of at least one user, said method comprising: enabling, at a computing device, an entity to generate an offer for one or more users by analysing plurality of discussions between the one or more users and the entity, wherein the offer includes one or more defined actions; in response to a communication received from the at least one user selected from the one or more users, enabling, at the computing device, the at least one user to accept the offer, wherein on acceptance of the offer, the at least one user confirms to perform the one or more defined actions; assessing, at the computing device, behaviour of the at least one user towards the one or more defined actions to determine whether the accepted offer is complied by the at least one user; and determining, at the computing device, a reputation score of the at least one user based on the assessment of the behaviour of the at least one user towards the one or more defined actions.

[00025] Various objects, features, aspects and advantages of the inventive subject matter will become more apparent from the following detailed description of preferred embodiments, along with the accompanying drawing figures in which like numerals represent like components. BRIEF DESCRIPTION OF THE DRAWINGS

[00026] FIG. 1 illustrates an exemplary network architecture showing one or more users and how the one or more users interact with the system and the entity in accordance with an embodiment of the present disclosure.

[00027] FIG. 2 illustrates exemplary functional components of the proposed system in accordance with an embodiment of the present disclosure.

[00028] FIG. 3A and FIG. 3B illustrate exemplary examples showing working of the system, in accordance with an exemplary embodiment of the present disclosure.

[00029] FIG. 4 illustrates an exemplary representation of working of the system, in accordance with an exemplary embodiment of the present disclosure.

[00030] FIG. 5 illustrates an exemplary representation when the user actually registers to the system in accordance with an embodiment of the present disclosure.

[00031] FIG. 6 illustrates an exemplary representation showing user details when the entity or other user actually views the details of the user in accordance with an embodiment of the present disclosure.

[00032] FIG. 7 illustrates an exemplary representation showing how a user can accept or reject an offer made by the entity in accordance with an embodiment of the present disclosure.

[00033] FIG. 8 illustrates an exemplary representation showing modification in the reputation score when the user dissociates with the entity in accordance with an embodiment of the present disclosure.

[00034] FIG. 9 illustrates a method for dynamically managing reputation of at least one user in accordance with an embodiment of the present disclosure.

[00035] FIG. 10 illustrates an exemplary computer system in which or with which embodiments of the present disclosure can be utilized in accordance with embodiments of the present disclosure.

DETAILED DESCRIPTION

[00036] The following is a detailed description of embodiments of the disclosure depicted in the accompanying drawings. The embodiments are in such detail as to clearly communicate the disclosure. However, the amount of detail offered is not intended to limit the anticipated variations of embodiments; on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present disclosure as defined by the appended claims.

[00037] In the following description, numerous specific details are set forth in order to provide a thorough understanding of embodiments of the present invention. It will be apparent to one skilled in the art that embodiments of the present invention may be practiced without some of these specific details.

[00038] Embodiments of the present invention include various steps, which will be described below. The steps may be performed by hardware components or may be embodied in machine- executable instructions, which may be used to cause a general-purpose or special-purpose processor programmed with the instructions to perform the steps. Alternatively, steps may be performed by a combination of hardware, software, and firmware and/or by human operators.

[00039] Embodiments of the present invention may be provided as a computer program product, which may include a machine-readable storage medium tangibly embodying thereon instructions, which may be used to program a computer (or other electronic devices) to perform a process. The machine- readable medium may include, but is not limited to, fixed (hard) drives, magnetic tape, floppy diskettes, optical disks, compact disc read-only memories (CD-ROMs), and magneto -optical disks, semiconductor memories, such as ROMs, PROMs, random access memories (RAMs), programmable read-only memories (PROMs), erasable PROMs (EPROMs), electrically erasable PROMs (EEPROMs), flash memory, magnetic or optical cards, or other type of media/machine-readable medium suitable for storing electronic instructions (e.g., computer programming code, such as software or firmware).

[00040] Various methods described herein may be practiced by combining one or more machine- readable storage media containing the code according to the present invention with appropriate standard computer hardware to execute the code contained therein. An apparatus for practicing various embodiments of the present invention may involve one or more computers (or one or more processors within a single computer) and storage systems containing or having network access to computer program(s) coded in accordance with various methods described herein, and the method steps of the invention could be accomplished by modules, engines, routines, subroutines, or subparts of a computer program product.

[00041] If the specification states a component or feature "may", "can", "could", or "might" be included or have a characteristic, that particular component or feature is not required to be included or have the characteristic. [00042] As used in the description herein and throughout the claims that follow, the meaning of

[00043] Exemplary embodiments will now be described more fully hereinafter with reference to the accompanying drawings, in which exemplary embodiments are shown. These exemplary embodiments are provided only for illustrative purposes and so that this disclosure will be thorough and complete and will fully convey the scope of the invention to those of ordinary skill in the art. The invention disclosed may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Various modifications will be readily apparent to persons skilled in the art. The general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the invention. Moreover, all statements herein reciting embodiments of the invention, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future (i.e., any elements developed that perform the same function, regardless of structure). Also, the terminology and phraseology used is for the purpose of describing exemplary embodiments and should not be considered limiting. Thus, the present invention is to be accorded the widest scope encompassing numerous alternatives, modifications and equivalents consistent with the principles and features disclosed. For purpose of clarity, details relating to technical material that is known in the technical fields related to the invention have not been described in detail so as not to unnecessarily obscure the present invention.

[00044] Thus, for example, it will be appreciated by those of ordinary skill in the art that the diagrams, schematics, illustrations, and the like represent conceptual views or processes illustrating systems and methods embodying this invention. The functions of the various elements shown in the figures may be provided through the use of dedicated hardware as well as hardware capable of executing associated software. Similarly, any switches shown in the figures are conceptual only. Their function may be carried out through the operation of program logic, through dedicated logic, through the interaction of program control and dedicated logic, or even manually, the particular technique being selectable by the entity implementing this invention. Those of ordinary skill in the art further understand that the exemplary hardware, software, processes, methods, and/or operating systems described herein are for illustrative purposes and, thus, are not intended to be limited to any particular named element.

[00045] It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussion, it is appreciated that throughout the description, discussions utilizing terms such as "computing", "comparing", "determining", "adjusting", "applying", "creating", "ranking," "classifying," or the like, refer to the actions and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (e.g., electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.

[00046] Certain embodiments of the present invention also relate to an apparatus for performing the operations herein. This apparatus may be constructed for the intended purposes, or it may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as, but not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions.

[00047] It is to be understood that the above description is intended to be illustrative, and not restrictive. Many other embodiments will be apparent to those of skill in the art upon reading and understanding the above description. The scope of the invention should therefore be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.

[00048] It should be apparent to those skilled in the art that many more modifications besides those already described are possible without departing from the inventive concepts herein. The inventive subject matter, therefore, is not to be restricted except in the spirit of the appended claims. Moreover, in interpreting both the specification and the claims, all terms should be interpreted in the broadest possible manner consistent with the context. In particular, the terms "comprises" and "comprising" should be interpreted as referring to elements, components, or steps in a non-exclusive manner, indicating that the referenced elements, components, or steps may be present, or utilized, or combined with other elements, components, or steps that are not expressly referenced. Where the specification claims refers to at least one of something selected from the group consisting of A, B, C ....and N, the text should be interpreted as requiring only one element from the group, not A plus N, or B plus N, etc.

[00049] In the foregoing description, numerous details are set forth. It will be apparent, however, to one of ordinary skill in the art having the benefit of this disclosure, that the present invention may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form, rather than in detail, to avoid obscuring the present invention.

[00050] Some portions of the detailed description have been presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. An algorithm is here, and generally, conceived to be a self-consistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.

[00051] It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussion, it is appreciated that throughout the description, discussions utilizing terms such as "computing", "comparing", "determining", "adjusting", "applying", "creating", "ranking," "classifying," or the like, refer to the actions and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (e.g., electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.

[00052] Each of the appended claims defines a separate invention, which for infringement purposes is recognized as including equivalents to the various elements or limitations specified in the claims. Depending on the context, all references below to the "invention" may in some cases refer to certain specific embodiments only. In other cases it will be recognized that references to the "invention" will refer to subject matter recited in one or more, but not necessarily all, of the claims. [00053] All methods described herein can be performed in any suitable order unless otherwise indicated herein or otherwise clearly contradicted by context. The use of any and all examples, or exemplary language (e.g., "such as") provided with respect to certain embodiments herein is intended merely to better illuminate the invention and does not pose a limitation on the scope of the invention otherwise claimed. No language in the specification should be construed as indicating any non-claimed element essential to the practice of the invention.

[00054] Various terms as used herein are shown below. To the extent a term used in a claim is not defined below, it should be given the broadest definition persons in the pertinent art have given that term as reflected in printed publications and issued patents at the time interval of filing.

[00055] The present disclosure is directed towards to a system that dynamically and in real-time manages and updates reputation of one or more users based on their commitment behaviour for defined action(s).According to an aspect of the present disclosure, a system for dynamically managing reputation of at least one user includes a non-transitory storage device having embodied therein one or more routines operable to dynamically manage reputation of the at least one user; and one or more processors coupled to the non-transitory storage device and operable to execute the one or more routines, wherein the one or more routines include: an offer generation engine, which when executed by the one or more processors, enables an entity to generate an offer for one or more users by analysing plurality of discussions between the one or more users and the entity, wherein the offer includes one or more defined actions; an offer acceptance engine, which when executed by the one or more processors, in response to a communication received from the at least one user selected from the one or more users, enables the at least one user to accept the offer, wherein on acceptance of the offer, the at least one user confirms to perform the one or more defined actions; a commitment behaviour assessment engine, which when executed by the one or more processors, assesses behaviour of the at least one user towards the one or more defined actions to determine whether the accepted offer is complied by the at least one user; and a commitment behaviour based reputation score management engine, which when executed by the one or more processors, computes a reputation score of the at least one user based on the assessment of the behaviour of the at least one user towards the one or more defined actions.

[00056] In an aspect, the entity is any of an organization, a land owner, a supplier of goods or a service provider, which may require the one or more users to perform the one or more defined actions. Therefore, the users for example, may be employee of the organization, tenants of the land-owner or customers of the supplier of goods or a service provider. Further, the entity can include, but not limited to employers, banks and land owners that may require reputation score for behavioural modelling of the user. This may aid the entity to evaluate potential risks in the activities of recruitment, providing loans, giving tenancy and to determine creditworthiness of the user.

[00057] In an exemplary aspect, the proposed system can include a registration engine that enables the user and the entity to register with the system and further verify and authorize each registered user and entity. The registration engine can further be configured such that no user can register more than once, which otherwise is possible in existing registration architectures where a user can register with a system through two or more email ids or phone numbers. This can be achieved by mandating the requirement of any or a combination of a mobile number, photograph, or Aadhaar Card/social security number, or PAN card, or a biometric or any other such unique identifier based input such as date of birth, place of birth and last name, based on which the system can verify/screen each new user to confirm if the same user has already registered with the system. System of the present disclosure can therefore be configured such that no user can have 2 accounts with the system and therefore the reputation associated with each user is legitimate, accurate, and reliable. Those skilled in the art would appreciate that the registration engine may register the one or more users using user details provided by respective one or more users, however, verification and authorization may be performed based on the unique identification associated with the user that may be generated based on the unique identifier such as Aadhaar Card/social security number, PAN number, biometric, and the like.

[00058] In an aspect, the registration engine may perform verification and authorization of each user by conducting a background check of user details provided by each user. The registration engine can conduct a background check of the details provided by the user using information such as TDS certificates, provident fund account details and bank accounts details to determine authenticity of the details provided by the user. The information such as TDS certificates, provident fund account details and bank accounts details can further be obtained by the registration engine using unique identifier such as a PAN card or an Aadhaar card. For example, if a user provides a user detail that he has worked in an organization for 2 years, the authenticity of this information can be checked using TDS certificates, provident fund account details or bank account details which can be obtained by using unique identifier such as a PAN card or an Aadhaar card. In an aspect, the registration engine of the present system can maintain verification and authorization status of the user details provided by the user along with the date on which the user details were last verified. [00059] In an aspect, the registration engine can further provide ability to the user to modify his/her details. In an embodiment, the user registration engine can also be used to disable or mark the user account as unverified for reasons such as registration with false details. Say for example, a user tries to register with incorrect details; the registration engine by using the unique identifier may check for duplication of the user and correct details. On finding a mismatch, the registration engine will disable the new registration.

[00060] In an aspect, the registration engine of the present system can provide a user with a default user badge. In another aspect, the registration engine can provide a user with an option to create a user badge. The user badge can further be adopted on any third party applications such as recruitment portals, emails, and the like. In an embodiment, the user badge can be chosen from variety of graphics such as letters, images, icons and the like presented to the user. Adopting user badge on third party applications enables the entity to view user details with an updated reputation score directly from the third party application. Those skilled in the art would appreciate that the above mentioned aspects of the registration engine can be extended to registration of entities such that even registered entities can be verified and authorized.

[00061] In an aspect, an offer generation engine of the proposed system can enable the entity to generate offer based on one or more prior discussions between the user and the entity. The one or more prior discussions between the user and the entity can be in oral or in written form. In an aspect, the offer can include one or more defined actions. The one or more defined actions may include any or a combination of reporting to the entity on a specified joining date, attending premises of the entity for a pre-defined duration, tasks to be performed in a pre-defied duration, maintaining confidentiality while performing tasks, serving a notice period on deciding to dissociate with the entity or any other terms, which the entity requires the one or more user to perform. Therefore, when the entity is an employer or an organization, the offer can include terms of employment such as joining date, office timings, designation, confidentiality clauses, role, responsibility, notice period, among other clauses as deemed appropriate by an employer.

[00062] In an aspect, in response to a communication received from the user, the offer acceptance engine enables the user to accept the offer. On acceptance of the offer, the user confirms to perform the one or more defined actions. The acceptance by the offer acceptance engine can include confirmation from the user that he/she would join the entity at a defined date. Such date can either be explicitly mentioned by the system or by the user at the time of acceptance or can be deemed to be applicable based on the date mentioned by the entity in the offer itself. In an example, the acceptance of the offer may be performed through a process whereby the user enters his/her name (as used during registration by the registration engine) i.e. deemed to be digitally signed, which may be followed by a one-time password verification on mobile phone and / or e-mail ID of the user.

[00063] In another exemplary aspect, the proposed system can include an offer rejection engine that enables the user to reject the offer with or without citing the reason. System may alternatively not include such an engine and rejection may be construed automatically if the offer is not accepted within a defined timeline of say 36 hours from the time of offer. In an aspect, the system can be configured to give periodical reminders to accept an offer within the defined timeline. For example, the system can send reminders after every 12 hours and in case the offer is not accepted after sending 3 reminders, the offer can be deemed as not accepted. Further, in an embodiment, the offer rejection engine can ask/survey and store the reason of rejection. The said reasons can be used for further analysis of reputation score of the user or the entity.

[00064] In an aspect, the system can include a communication engine, which may enable the entity and the users to communicate with each other. For example, the user can communicate with entity through a comment box regarding the changes or amendments in the offer.

[00065] In an aspect, the commitment behaviour assessment engine can assess behaviour of the user towards the one or more defined actions to determine whether the accepted offer is complied by the user. For example, the commitment behaviour assessment engine can determine whether the user actually joined the entity on a defined date. Commitment behaviour assessment can further take into consideration behaviour of the user for a defined initial period of time after joining of the user with the entity. For instance, in a first example, commitment behaviour can be construed to have been honoured if the user/potential employee joins the entity at the mutually accepted date of joining and therefore formally becomes an employee of the entity. In a second example, along with construing whether the user joined the entity, system of the present disclosure can also monitor feedback/behaviour of the user for a defined initial period of time say 30 days from the date of joining to see if the user is meeting the desired expectations laid out by the entity at the time of offer or afterwards. In a third example, where entity is a bank, the commitment behaviour assessment engine can analyse whether the user has complied with the terms of opening the bank account or is timely repaying the loan amount.

[00066] In an aspect, a commitment behaviour based reputation score management engine can compute a reputation score based on the assessment of the behaviour of the user towards the one or more defined actions. For example, the reputation score can be varied depending on whether the user honours his/her commitment of joining the entity once an offer is accepted or not.

[00067] The present disclosure further relates to a method for dynamically managing reputation of at least one user, said method including enabling, at a computing device, an entity to generate an offer for one or more users by analysing plurality of discussions between the one or more users and the entity, wherein the offer includes one or more defined actions, in response to a communication received from the at least one user selected from the one or more users, enabling, at the computing device, the at least one user to accept the offer, wherein on acceptance of the offer, the at least one user confirms to perform the one or more defined actions, assessing, at the computing device, behaviour of the at least one user towards the one or more defined actions to determine whether the accepted offer is complied by the at least one user, and determining, at the computing device, a reputation score of the at least one user based on the assessment of the behaviour of the at least one user towards the one or more defined actions.

[00068] In another aspect, the reputation score can be based on other factors such as educational qualifications, period of work in an organization, designation, and the like.

[00069] In an aspect, all such scores can be managed automatically without user intervention and can also be validated by the system of the present disclosure to confirm accuracy thereof.

[00070] In an aspect, the reputation score can be represented in any manner, for instance, on a scale of 1-10, or across 5 stars, or in any other numeric, alphanumeric, graphical, image-based, or even subjective representation.

[00071] In an aspect, the reputation score of the user is increased when the accepted offer is complied by the user. For example, the reputation score of a user is increased when the user is compliant with the terms of the offer and joins the entity on or before the joining date.

[00072] In an aspect, the reputation score of the at least one user is decreased when the accepted offer is not-complied by the at least one user. For example, if the user A accepts an offer from El and later, accepts an offer from a second entity E2 through the proposed system, an intimation of such acceptance can be sent to entity El and simultaneously the reputation score of the user can be decreased.

[00073] In an aspect, the reputation score can also be decreased if the user fails to join the entity on the defined joining date but joins at a later date. In the said aspect, the reputation score can be varied depending on the reasons cited therefor.

[00074] In an aspect, the reputation score can also be determined and accordingly decreased if a user leaves the entity within a defined timeline of say 30 days after date of joining, without serving notice period. The notice period maybe calculated based on the information entered during acceptance of offer or last date of working in an organization entered by the user.

[00075] In an embodiment, the commitment behaviour based reputation score management engine may compute a reputation score of the entity based on attributes of the entity that may comprise any or a combination of employees working for the entity, working capital of the entity, infrastructure of the entity, customer service provided by the entity, intellectual capital of the entity and financial performance of the entity, and the like.

[00076] In an aspect, reputation score of an entity can be decreased on occurrence of events such as cancelling an offer, delaying date of joining, and the like.

[00077] In another aspect, the communication engine can allow user and/or entity to add comments/feedback for each other along with their experiences, which can be validated by the proposed system for their accuracy and then posted for public review.

[00078] Although other parameters such as average tenure of the user per company that he/she has worked with, accuracy of their claims on role/responsibility during interview, reliability of references shared, validity of educational qualifications, among others can be used for reputation score computation for the user, system of the present disclosure, as mentioned above, relies at least on commitment behaviour of the user towards an offer that was made by an entity and accepted by the user. The more the user is compliant to his commitments of joining an entity, higher would be the reputation score, whereas if the user accepts an offer and does not eventually joins the entity from which the offer was made, reputation goes down accordingly.

[00079] In an aspect, the reputation score of the user can be available to all entities interacting with the system. Illustratively, if a user C has accepted an offer from entity El, the system can be configured such that any other entity E2 may also be able to see the reputation score of the user C along with the fact that the user C has accepted another offer of entity El .

[00080] In an aspect, when an entity tries to make an offer to a user, the system can display user details and associated reputation scores to the entity. In an embodiment, the system can allow the entity to make an offer to an unregistered user. The unregistered user can then register for accepting or rejecting the offer. Further, in an embodiment, when the said unregistered user registers, the system can be enabled to automatically discover the historical offers made to the user in case the system has existing user details based on the unique identifier of the user. [00081] FIG. 1 illustrates an exemplary network architecture showing one or more users and how the one or more users interact with the system and the entity in accordance with an embodiment of the present disclosure.

[00082] As illustrated, the exemplary network architecture implements User Commitment

Behaviour Based Dynamic Reputation Management System (USBDRMS) (104), to dynamically and in real-time manage and update reputation of one or more users (106-1, 106-2... 106-N). The USBDRMS (104) is referred to as the system (104) herein after. The system (104) can be enabled to interact with entity (102) and one or more users (106-1, 106-2... 106-N). The entity (102) can be an organization or an employer who wants to enlist new employees. The entity can also be a land owner, a bank, a supplier of goods or a service provider that can provide services based on reputation of their customers to prevent frauds. The one or more users (106-1,106-2... 106-N) can be collectively referred to as users (106) and individually referred to as user (106). The users can be a new employee, a new tenant or a new client of an entity to whom offer is made.

[00083] In an aspect, the entity (102) and the users (106) can interact with the system (104) through computing devices such as a mobile phones, a smart phone, a tablet, personal computer, a laptop or other portable computers, a notebook, a Personal Digital Assistant (PDA), and the like. The computing devices can be connected to the system(104) though desired communication links such as a dial-up modem connection, cable links, digital subscriber lines (DSL), wireless or satellite links, or any other suitable form of communication links.

[00084] In an aspect, if an entity (102) desires to select either user (106-1) or user (106-2) to perform defined actions, the system (104) aids the entity (102) by providing updated reputation score of users (106-1) and (106-2)based on commitment behaviour along with other factors such as educational qualification, period of work in an organization, designation, and the like. Further, the commitment behaviour can be based on determination of various factors, say for example, whether the previous commitments accepted by the users (106-1) and (106-2) were honoured/met/complied, whether the users (106-1) and (106-2) actually joined the entity at the mutually accepted date of joining or not. On the account of reputation score, the entity (102) can compare user (106-1) and (106-2) and select the suitable user.

[00085] FIG. 2 illustrates exemplary functional components of the proposed system in accordance with an embodiment of the present disclosure. [00086] In an aspect, the system (104) may comprise one or more processor(s) 202. The one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that manipulate data based on operational instructions. Among other capabilities, the one or more processor(s) (202) are configured to fetch and execute computer-readable instructions stored in a memory (206) of the system (104). The memory (206) may store one or more computer-readable instructions or routines, which may be fetched and executed to create or share the data units over a network service. The memory (206) may comprise any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as EPROM, flash memory, and the like.

[00087] The system (104) may also comprise an interface(s) (204). The interface(s) (204) may comprise a variety of interfaces, for example, interfaces for data input and output devices, referred to as I/O devices, storage devices, and the like. The interface(s) (204) may facilitate communication of system (104). The interface(s) (204) may also provide a communication pathway for one or more components of the system (104). Examples of such components include, but are not limited to, processing engine(s) (208) and data (210).

[00088] The processing engine(s) (208) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s) (208). In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine(s) (208) may be processor executable instructions stored on a non-transitory machine- readable storage medium and the hardware for the processing engine(s) (208) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s) (208). In such examples, the system (104) may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to system (104) and the processing resource. In other examples, the processing engine(s) (208) may be implemented by electronic circuitry. [00089] The data (210) may comprise data that is either stored or generated as a result of functionalities implemented by any of the components of the processing engine(s) (208) or the system (104).

[00090] In an exemplary embodiment, the processing engine(s) (208) may include a registration engine (212), an offer generation engine (214), an offer acceptance engine (216), an offer rejection engine (218), a commitment behaviour assessment engine (220), a commitment behaviour based reputation score management engine (222) and other engine(s) (224).

[00091] In an embodiment, the registration engine (212) provides the users with an ability to register themselves directly with the system (104). The registration engine (212) can mandate requirement of any or a combination of a mobile number, photograph, or Aadhaar Card/social security number, or PAN card, or a biometric or any other such unique identifier based input such as date of birth, place of birth and last name, or a combination thereof, based on which the system (104) can verify /screen each new user by generating a unique identification to confirm if the same user has already registered with the system (104). This above mentioned technique can prevent multiplicity of accounts of the same user. Therefore, the system (104) can be configured such that no user can have 2 accounts with the system (104).

[00092] In an aspect, the registration engine (212) can further be configured to give ability to the users to modify their details. In an embodiment, the registration engine (212) can also be used to disable the user account for reasons such as registration with false details. Say for example, a user A tries to register with incorrect details, the system (104) by using a unique identifier will check for duplication of the user and correct details. On finding a mismatch, the system (104) will disable new registration of user A.

[00093] In an aspect, the registration engine (212) can provide the user with a default user badge. In another aspect, the registration engine (212) can provide the user with an option to create a user badge by selecting from a variety of graphics such as letters, images, icons, and the like which are presented to the user. The user badge can further be adopted on any third party applications such as recruitment portals, emails, and the like. Adopting user badge on third party applications enables the entity to view user details with an updated reputation score directly from the third party application.

[00094] In an aspect, the registration engine (212) can conduct a background check of details provided by the user using information such as TDS certificates, provident fund account details and bank accounts details to determine authenticity of the details provided by the user. The information such as TDS certificates, provident fund account details and bank accounts details can further be obtained by the system using unique identifier such as a PAN card or an Aadhaar card.

[00095] Those skilled in the art would appreciate that the above-mentioned aspects related to the registration engine (212) can also be utilized for registration of entities such that each registered entity can also be verified and authorized using the unique identifier in a similar manner as disclosed considering registration of the user.

[00096] In an aspect, the offer generation engine (214) can enable an entity to generate an offer for users. The offer can be generated based on one or more prior oral or written discussions between the users and the entity. The offer can include one or more defined actions that the user is expected to perform such as reporting to the entity on a specified joining date, attending premises of the entity for a pre-defined duration, tasks to be performed in a pre-defied duration, maintaining confidentiality while performing tasks, serving a notice period on deciding to dissociate with the entity. For example, the offer can include various terms of employment such as joining date, office timings, designation, confidentiality clauses, role, responsibility and notice period.

[00097] In an aspect, the offer acceptance engine (216) can be configured to enable at least one user to accept the offer made by the entity. The acceptance can include confirmation from the user to perform the defined actions e.g. he/she would join the entity at the defined date. Such date can either be explicitly mentioned by the system (104) or by the entity at the time of acceptance or can be deemed to be applicable based on the date mentioned by the entity in the offer itself. The acceptance can also include terms of employment confirmed by the user. In an example, the acceptance of the offer may be performed through a process whereby the user enters his name i.e. deemed to be digitally signed followed by one time password verification on mobile phone of the user.

[00098] In an exemplary aspect, the offer rejection engine (218) can enable the user to reject the offer with or without citing the reasons. Alternatively, the system (104) may not include such an engine and can give periodic reminders reminding the user to accept the offer within a defined timeline of say 36 hours from the time of offer. The rejection may be construed automatically if the offer is not accepted within the defined timeline. For example, the system (104) can send reminders after every 12 hours and in case the offer is not accepted after sending 3 reminders, the offer can be deemed as not accepted.

[00099] In an aspect, the commitment behaviour assessment engine (220) can assess behaviour of the user towards the defined actions to determine whether the accepted offer is complied by the user. For example, the commitment behaviour assessment engine (220) can assess whether the user actually joined the entity at the mutually accepted date of joining or not. Commitment behaviour can further take into consideration behaviour of the user for a defined initial period of time after joining of the user the entity. For example, commitment behaviour can be construed to have been honoured if the user joins the entity at the mutually accepted date of joining and therefore formally becomes an employee of the entity. In a second example, along with construing whether the user joined the entity, system (104) can also monitor feedback/behaviour of the user for a defined initial period of time say 30 days from the date of joining to see if the user is meeting the desired expectations laid out by the entity at the time of offer or afterwards.

[000100] In an aspect, the commitment behaviour based reputation score management engine (222) enables the system (104) to generate, update, and manage reputation score of user based on the assessment of the behaviour of the user towards the defined actions. In an aspect, reputation score can be increased whenever user honours his/her commitment of joining the entity once an offer is accepted, alternatively, reputation score can be decreased whenever the user dishonours by not joining the entity after having accepted the offer. In another aspect, the reputation score can be based on other factors such as educational qualifications, period of work in an organization, designation, and the like.

[000101] In an aspect, all such scores can be managed automatically without user intervention and can also be validated by the system (104) of the present disclosure to confirm accuracy thereof. In an aspect, reputation score can be represented in any manner, for instance, on a scale of 1-10, or across 5 stars, or in any other numeric, alphanumeric, graphical, image-based, or even subjective representation. The more the user is compliant to his commitments of joining an entity, higher would be the reputation score, whereas if the user accepts an offer and does not eventually joins the entity from which the offer was made, reputation score would decrease.

[000102] In an aspect, the reputation score of the user can be available to all entities interacting with the system (104). For example, if a user C has accepted an offer from entity El, system can be configured such that any other entity E2 may also be able to see the reputation score of the user C along with the fact that the user C has accepted another offer of entity El .

[000103] In an aspect, other engine(s) (224) may include a resignation engine, a notification engine, a notification engine, and a communication engine. The resignation engine can enable a user to dissociate from the entity. For example, the user can resign from current employer using the resignation engine by entering details such as resignation date and last working date. The entity can then accept or reject the resignation of user such that on acceptance of the resignation, a notice period can be calculated. The notification engine can provide notifications to the entity and the user. All alerts such as offers made, accepted, notice period, resignation or any other alerts may be communicated using the notification engine. For example, the entity can be notified when the user resigns and the user can be notified of acceptance or rejection of the resignation. The commitment behaviour based reputation score management engine (222) can update reputation score of the user based on whether the notice period being served or not. For example if user A resigns on March 1 and his resignation was accepted by entity B on the same day, the notice period of 30 days may begin. On March 31, system may send a notification to user and entity querying if notice period was served. The reputation score can be increased or decreased accordingly.

[000104] In an aspect, the communication engine can enable communications among various entities, among various users, or among entities and users. For example, the entities can discuss and communicate with each other regarding user and his background. The entity and the user can discuss the offer and define actions to be performed by the user.

[000105] In an aspect, the data 210 can store entire history of each user including offers received by the user, offers rejected by the user, entity associated with the user, duration of such association, etc.

[000106] FIG. 3A and FIG. 3B illustrate exemplary examples showing working of the system, in accordance with an exemplary embodiment of the present disclosure.

[000107] In an exemplary embodiment, as illustrated in FIG. 3A, an entity (302) can generate an offer using the offer generation engine (214), further, a user (310) can accept the offer citing a joining date using the offer acceptance engine (216). When the user (310) is compliant with the terms of the offer and joins the entity on or before the said joining date, the system (104) can increase the reputation score.

[000108] This above mentioned embodiment can be further explained with the help of an example, say for example, if a user A accepts an offer using the offer acceptance engine (216) of the present disclosure from entity El on l 'st Jan 2017 and confirms joining on l 'st May 2017, and then actually joins the entity El on 1 'st March 2017, user A's reputation score would be increased or maintained.

[000109] In an exemplary embodiment, as illustrated in FIG. 3B, an entity (302) can generate an offer using the offer generation engine (214), further, a user (310) can accept the offer citing a joining date using the offer acceptance engine (216). If the user (310) accepts another offer given by another entity other than the said entity (302) before the said joining date and the user(310) joins another entity other than the said entity (302), the system (104) can intimate the entity (302) that user (310) has joined another entity and also, decrease the reputation score.

[000110] This above mentioned embodiment can be further explained with the help of an example, say for example, if the user A accepts another offer from El and later, accepts an offer from a second entity E2 through the proposed system, an intimation of such acceptance can be sent to entity El as well along with enabling the system to decrease the reputation score of the user A.

[000111] In an aspect, the reputation score can also be decreased if the user fails to join the entity on the defined joining date but joins at a later date. Say for example, in an offer the defined date of joining on 1st March 2017, however, the user joins the entity on 3rd March 2017, the reputation score is decreased. Also, in the said example the reputation score can be varied depending on the reasons cited therefor.

[000112] In an aspect, the reputation score can also be decreased if a user leaves the entity within a defined timeline of say 30 days or without serving a minimum notice period as defined by the entity after date of joining. For example a user joins an organization on defined date of joining of 1st March 2017 but leaves the entity of 8th March 2017, the reputation score is decreased, as per the pre defined system conditions. The reputation score can further be varied depending on the reasons cited thereof. In an aspect, the notice period may be calculated based on the information entered during acceptance of offer.

[000113] In an exemplary embodiment, the reputation score of an entity can also be managed and updated by the system (104). The reputation score of the entity can be based on number of employees working in the entity, working capital, infrastructure, customer service, intellectual capital, financial performance, and the like.

[000114] In an aspect, the reputation score of the entity can be decreased on occurrence of events such as cancelling the offer, delaying the date of joining, and the like. For example, if an entity El gives an offer to user B on l 'st Jan 2017 and mentions the joining date of l 'st March 2017, which user B accepts, and then the entity El cancels the offer or delays the joining date to say l 'st May 2017, reputation score of the entity can be decreased.

[000115] FIG. 4 illustrates an exemplary representation of working of the system, in accordance with an exemplary embodiment of the present disclosure.

[000116] As illustrated, in an aspect, at step (402), an entity can login to the User Commitment Behaviour Based Dynamic Reputation Management System (USBDRMS), herein referred as the system, using entity details such as PAN card, company name, company address, and the like. Verification of the entity can be done using an e-mail or an sms at step (404), for example, the verification can be done using a one-time password that is valid for only one login session. Once verified, at step (406), the entity can search for a user. The search can be performed using user details such as user name or e-mail address or PAN number, Aadhaar number or any other unique identifier. If the said user has registered on the system previously, the system can provide the entity with the user details along with the reputation score at step (414). On the other hand, if the said user has not registered on the system previously, according to step (412), the system can register the user using user registration engine as explained in the above mentioned embodiments.

[000117] Once the system recognizes the user, the offer generation engine can generate an offer using above mentioned embodiments, at step (416). Subsequently, the user can login into the USBDRMS at step (418), and user verification can be done using an e-mail and OTP sms and/ or OTP on email verification for example, by using a one-time password at step (420). After a successful login, the user can accept or reject the offer, at step (422). If the user rejects an offer, the notification can be sent to the entity along with the reasons cited therefor, at step (424). If the user accepts the offer, a reminder can be sent to the entity as well as the user before the defined joining date, at step (428). The later steps can be performed based on whether the user joins the entity on the defined joining date or not. In an aspect, if the user joins an entity on the defined joining date, the system can monitor the feedback/behaviour of the user for instance, say 30 days as depicted at step (432), based on which the reputation score can be updated at step (434). In another aspect, if the user does not join the entity on the defined joining date, a notification can be sent to the entity as well as the user at step (430) and the reputation score can be updated accordingly, based on the reasons cited therefor, at step (434).

[000118] FIG. 5 illustrates an exemplary representation when the user actually registers to the system in accordance with an embodiment of the present disclosure.

[000119] For registration of a user, the proposed system or the proposed registration engine can require details that can be optional or mandatory. The optional details may include educational qualification (506), photograph (512), and the like. The mandatory details may include name (502), date of birth (504), and the like. After providing the optional and mandatory details, the user can register using a sign up button (518) once user accepts terms and conditions and verifies his / her email and mobile number. [000120] In an aspect, the present system can provide the user with a default user badge. In another aspect, the registration engine can provide the user with an option to create a user badge. The user badge can further be adopted on any third party applications such as recruitment portals, emails, and the like. In an embodiment, the user badge can be chosen from variety of graphics such as letters, images, icons, and the like which are presented to the user by the system. Adopting user badge on third party applications enables the entity to view user details with an updated reputation score directly from the third party application.

[000121] In an aspect, the proposed system can be further configured such that any user is not able to create two or more accounts. This can be achieved by mandating the requirement of any or a combination of mobile number, photograph, or Aadhaar Card/social security number, or PAN card, or biometric or any other such unique identifier based input, such as date of birth, place of birth and last name or a combination thereof, based on which the system can verify/screen each new user to confirm if the same user has already registered with the system. For example, as illustrated in FIG.5 the requirement of at least one identity proof number (PAN/Voter ID/Aadhaar number) (514) can be made mandatory. This above mentioned technique aids in avoiding the registration of the same user more than once in order to achieve legitimate, accurate and reliable reputation score associated with each user.

[000122] In an aspect, the system can conduct a background check of details provided by the user using information such as TDS certificates, provident fund account details and bank accounts details to determine authenticity of the details provided by the user. The information such as TDS certificates, provident fund account details and bank accounts details can further be obtained by the system using unique identifier such as a PAN card or an Aadhaar card (514). To provide clarity, this can further be explained with the help of an example, for example, if a user A provides information that he has worked in an organization B for 2 years, the authenticity of this information can be checked using TDS certificates, provident fund account details or bank account details which can be obtained by using unique identifier such as a PAN card or an Aadhaar card.

[000123] In an aspect, the present system can be further configured to maintain a verification status of the user details provided by the user along with the date on which the user details were last verified.

[000124] FIG. 6 illustrates an exemplary representation showing user details when the entity or other user actually views the details of the user in accordance with an embodiment of the present disclosure. Illustrated are the details when an entity or a user views the details of a user "ABC" (604). When an entity views user details of a user, it can observe all corresponding details with which the user has registered along with the reputation score. The reputation score can be represented in any manner, for instance, on a scale of 1-10, or across 5 stars, or in any other numeric, alphanumeric, graphical, image-based, or even subjective representation. In FIG. 6 the reputation score of 8 on a scale of 10 is shown at 610. This reputation score can be represented in any manner, for instance, on a scale of 1-10, or across 5 stars, or in any other numeric, alphanumeric, graphical, image-based, or even subjective representation.

[000125] In an aspect, when an entity tries to make an offer to a user, the system can discover user details and its associated reputation score and make it available to the entity. In an embodiment, the system can allow the entity to make an offer to an unverified user who has registered on the system. The unverified user can then verify using registration engine for accepting or rejecting the offer. Further, in an embodiment, when the said unregistered user registers, the system can be enabled to automatically discover the historical offers made to the user in case the system has existing user details. To clarify, the registered user is any user who has provided user details such as name, date of birth, mobile number and on the like and who may have verified his mobile number and email address to create a user account. However, verified user may be a registered user who has been assigned a unique identification based on credentials such as PAN number, Aadhaar number, and the like. Thus, a registered user may not be able to accept or reject any offers until he/she has been verified. Similarly, a registered entity if an employer may not send offers to the user until company account is verified.

[000126] In an aspect, as shown in FIG.6, the entity can view relevant information such as current organization (612), current designation (614) and previous employment details (616) including but not limited to organization and period of work. These details may enable the entity to take an informed decision pertaining to selection of a credible employee.

[000127] In an aspect, parameters such as average tenure of the user per company that he/she has worked with, accuracy of their claims on role/responsibility during interview, reliability of references shared, validity of educational qualifications, among others can be used for computation of reputation score of the user and such details can be shown while viewing the user details.

[000128] FIG. 7 illustrates an exemplary representation showing how a user can accept or reject an offer made by the entity in accordance with an embodiment of the present disclosure.

[000129] In an aspect, after analysing the user details as illustrated in FIG. 6, the entity can generate an offer using the offer generation engine (214). On generation of the offer the user may be presented an offer letter (702) that includes defined actions to be performed by the user on his/her association with the entity. The user may go through the offer details and may negotiate with the entity using the communication engine that can provide a comment box or a chat option to the user. Further, the user may either accept the offer using "Verify digital signature to accept the offer" (704) or reject the offer using "Reject" (706). For accepting the offer, the user can upload his/her digital signature that can be followed by entering a one-time password received on mobile device of the user. After the offer is accepted, the commitment behaviour assessment engine (220) may assess the subsequent actions of the user to analyse if the user is complying with the defined actions accepted by the user. Based on said assessment, the reputation score may be generated.

[000130] FIG. 8 illustrates an exemplary representation showing modification in the reputation score when the user dissociates with the entity in accordance with an embodiment of the present disclosure.

[000131] In an aspect, when a user dissociates with the entity, for example, the user resigns, the entity can either accept or reject the resignation. When the entity accepts the resignation, the notice period of the user may begin. Further, at the end of the notice period the system (104) can be notified that whether the notice period was served or not, based on which the reputation score of the user can be updated.

[000132] According to an example as illustrated in FIG.8, the when a user "ABC" dissociates from the entity "XYZ". The system (104) can analyse period for which the user was associated with the entity and can also analyse whether the notice period was served or not using the table 802. Further, based on said analyses, the system (104) can update the reputation score of the user ay 804.

[000133] FIG. 9 illustrates a method for dynamically managing reputation of at least one user in accordance with an embodiment of the present disclosure.

[000134] In an aspect, the proposed method may be described in general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, engines, modules, functions, etc., that perform particular functions or implement particular abstract data types. The method can also be practiced in a distributed computing environment where functions are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, computer executable instructions may be located in both local and remote computer storage media, including memory storage devices. [000135] The order in which the method as described is not intended to be construed as a limitation, and any number of the described method blocks may be combined in any order to implement the method or alternate methods. Additionally, individual blocks may be deleted from the method without departing from the spirit and scope of the subject matter described herein. Furthermore, the method may be implemented in any suitable hardware, software, firmware, or combination thereof. However, for ease of explanation, in the embodiments described below, the method may be considered to be implemented in the above described system.

[000136] According to an aspect, the method includes, at block 902, enabling an entity to generate an offer for one or more users. The offer may be generated by analysing plurality of discussions between the one or more users and the entity and may include one or more defined actions. In response to a communication received from the at least one user selected from the one or more users, at block 904, the at least one user may be enabled to accept the offer. On acceptance of the offer, the at least one user confirms to perform the one or more defined actions.

[000137] According to an aspect, the method includes, at block 906, assessing behaviour of the at least one user towards the one or more defined actions to determine whether the accepted offer is complied by the at least one user. Further, at block 908, a reputation score of the at least one user is determined based on the assessment of the behaviour of the at least one user towards the one or more defined actions.

[000138] Those skilled in the art would appreciate that though embodiments of the present disclosure is explained considering employers or organizations as entities and employees as users, however, the scope of the present disclosure is not limited to employer-employee relationship. Thus, embodiments of the present disclosure can also be utilized to manage reputation of users for private contracts e.g. between supplier and customers for companies, clients and contractor contracts, job orders and any such contracts that entail process of offer acceptance.

[000139] FIG. 10 illustrates an exemplary computer system in which or with which embodiments of the present disclosure can be utilized in accordance with embodiments of the present disclosure.

[000140] As shown in FIG. 10, computer system includes an external storage device (1010), a bus (1020), a main memory (1030), a read only memory (1040), a mass storage device (1050), communication port (1060), and a processor (1070). A person skilled in the art will appreciate that computer system may include more than one processor and communication ports. Examples of processor (1070) include, but are not limited to, an Intel® Itanium® or Itanium 2 processor(s), or AMD® Opteron® or Athlon MP® processor(s), Motorola® lines of processors, FortiSOC™ system on a chip processors or other future processors. Processor (1070) may include various engines associated with embodiments of the present invention. Communication port (1060) can be any of an RS-232 port for use with a modem based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. Communication port (1060) may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which computer system connects.

[000141] Memory (1030) can be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. Read only memory (1040) can be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or BIOS instructions for processor (1070). Mass storage (1050) may be any current or future mass storage solution, which can be used to store information and/or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and/or Firewire interfaces), e.g. those available from Seagate (e.g., the Seagate Barracuda 7102 family) or Hitachi (e.g., the Hitachi Deskstar 7K1000), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g. an array of disks (e.g., SATA arrays), available from various vendors including Dot Hill Systems Corp., LaCie, Nexsan Technologies, Inc. and Enhance Technology, Inc.

[000142] Bus (1020) communicatively couples processor(s) (1070) with the other memory, storage and communication blocks. Bus (1020) can be, e.g. a Peripheral Component Interconnect (PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), USB or the like, for connecting expansion cards, drives and other subsystems as well as other buses, such a front side bus (FSB), which connects processor (1070) to software system.

[000143] Optionally, operator and administrative interfaces, e.g. a display, keyboard, and a cursor control device, may also be coupled to bus (1020) to support direct operator interaction with computer system. Other operator and administrative interfaces can be provided through network connections connected through communication port (1060). External storage device (1010) can be any kind of external hard-drives, floppy drives, IOMEGA® Zip Drives, Compact Disc - Read Only Memory (CD- ROM), Compact Disc - Re-Writable (CD-RW), Digital Video Disk - Read Only Memory (DVD-ROM). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system limit the scope of the present disclosure.

[000144] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.

ADVANTAGES OF THE PRESENT DISCLOSURE

[000145] The present disclosure provides systems and methods that analyse commitment behaviour of one or more users with an entity.

[000146] The present disclosure provides systems and methods that manage reputation of one or more users based on their commitment behaviour.

[000147] The present disclosure provides systems and methods to compute reputation score of the user to determine creditworthiness of the user.

Claims

I Claim:

1. A system for dynamically managing reputation of at least one user, said system comprising:

a non-transitory storage device having embodied therein one or more routines operable to dynamically manage reputation of the at least one user; and

one or more processors coupled to the non-transitory storage device and operable to execute the one or more routines, wherein the one or more routines include:

an offer generation engine, which when executed by the one or more processors, enables an entity to generate an offer for one or more users by analysing plurality of discussions between the one or more users and the entity, wherein the offer includes one or more defined actions;

an offer acceptance engine, which when executed by the one or more processors, in response to a communication received from the at least one user selected from the one or more users, enables the at least one user to accept the offer, wherein on acceptance of the offer, the at least one user confirms to perform the one or more defined actions;

a commitment behaviour assessment engine, which when executed by the one or more processors, assesses behaviour of the at least one user towards the one or more defined actions to determine whether the accepted offer is complied by the at least one user; and

a commitment behaviour based reputation score management engine, which when executed by the one or more processors, computes a reputation score of the at least one user based on the assessment of the behaviour of the at least one user towards the one or more defined actions.

2. The system of claim 1, wherein the system further comprises a registration engine, which when executed by the one or more processors, enables any or a combination of the entity or the one or more users to register with the system, and further verify and authorize each registered user and the registered entity.

3. The system of claim 2, wherein the registration engine registers the one or more users based on user details provided by respective one or more users and wherein each user is verified and authorized based on a unique identifier associated with said user.

4. The system of claim 2, wherein the registration engine performs verification and authorization of each user by conducting a background check of user details provided by each user.

5. The system of claim 1, wherein the one or more defined actions comprises any or a combination of reporting to the entity on a specified joining date, attending premises of the entity for a pre-defined duration, tasks to be performed in a pre-defied duration, maintaining confidentiality while performing tasks, serving a notice period on deciding to dissociate with the entity or any other terms, which the entity requires the one or more user to perform.

6. The system of claim 1, wherein the entity is any of an organization, a land owner, a supplier of goods or a service provider, which require the one or more users to perform the one or more defined actions.

7. The system of claim 1, wherein the commitment behaviour assessment engine assesses behaviour of the at least one user towards the one or more defined actions for a pre-defined duration.

8. The system of claim 1, wherein the reputation score of the at least one user is increased when the accepted offer is complied by the at least one user and the reputation score of the at least one user is decreased when the accepted offer is not-complied by the at least one user.

9. The system of claim 1, wherein the commitment behaviour based reputation score management engine computes a reputation score of the entity based on attributes of the entity comprising any or a combination of employees working for the entity, working capital of the entity, infrastructure of the entity, customer service provided by the entity, intellectual capital of the entity and financial performance of the entity.

10. A method for dynamically managing reputation of at least one user, said method comprising: enabling, at a computing device, an entity to generate an offer for one or more users by analysing plurality of discussions between the one or more users and the entity, wherein the offer includes one or more defined actions;

in response to a communication received from the at least one user selected from the one or more users, enabling, at the computing device, the at least one user to accept the offer, wherein on acceptance of the offer, the at least one user confirms to perform the one or more defined actions;

assessing, at the computing device, behaviour of the at least one user towards the one or more defined actions to determine whether the accepted offer is complied by the at least one user; and

determining, at the computing device, a reputation score of the at least one user based on the assessment of the behaviour of the at least one user towards the one or more defined actions.