Sign In to Follow Application
View All Documents & Correspondence

System And Method For Facilitating Interaction Between Users Operating On Separate Protocols Over A Network Interface

Abstract: ABSTRACT Title.: Method of capturing, processing and authenticating user information over a plurality of nodes in a network and a system there-for The present invention provides a system and method of capturing, processing and authenticating user information over a plurality of nodes in a network wherein each of the plurality of nodes operate on at least one protocol. In an embodiment, each of the plurality of nodes operate on different protocol than one another.

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
28 October 2013
Publication Number
29/2015
Publication Type
INA
Invention Field
COMMUNICATION
Status
Email
shivendra@krishnaandsaurastri.com
Parent Application

Applicants

Emart Solutions India Private Limited
2nd Floor, Malhotra House, Next to Tata Motors Showroom, Marwa Industrial Estate, Off Saki Vihar Road, Sakinaka, Mumbai – 400072

Inventors

1. Srikanth Chunduri
2nd Floor, Malhotra House, Next to Tata Motors Showroom, Marwa Industrial Estate, Off Saki Vihar Road, Sakinaka, Mumbai – 400072
2. Aditya Bhamidipaty
2nd Floor, Malhotra House, Next to Tata Motors Showroom, Marwa Industrial Estate, Off Saki Vihar Road, Sakinaka, Mumbai – 400072

Specification

DESC:Field of the Invention
The present invention generally relates to a system and method for standardizing and mapping protocols. More particularly, the present invention provides a system and method of capturing, processing and authenticating user information over a plurality of nodes in a network wherein each of the plurality of nodes operate on at least one protocol.
Background of the Invention
A typical enterprise system enables the launch of several new ideas, programs, user authentication, user validation, transaction validation and other target applications into one single system. The key purpose of such a system is the ability to rapidly scale data processing and automate relevant responses leading to faster turnarounds, and collect the right data and store the data in the right databases within the system.
Incompatibility of data record identifiers in the various datasheets shared between various Interfaces is a problem. Each interface, typically, defines its own data identifiers. The problem arises when two or more interfaces define the same data record through multiple and distinct definitions. There is no way for the interfaces to transfer data records and parse the records accurately in such cases. This is because, an interface does not have the intelligence to map its own record identifier to a record identifier from another interface, even if the data record was fundamentally judged to be the same by a human. This is a lack of intelligence in the interfaces and leads to incorrect or abandoned parsing of data records, thereby decelerating the scalability of the said automated technology system. This also leads to incorrect, insufficient or irrelevant data capture, data storage and data retrieval of the metadata and data records.
Absence of a system for authenticating and validating data records and interface users using a unique identity capable of ascertaining identity as well as authority to transmit and receive data records.
Currently, the problem of data incompatibility is solved via manual intervention. The problem of the lack of capability to ascertain unique identity is an unsolved one. Some of the common surrogate methods used to attempt to achieve ascertainment of unique identification include using email ids, mobile numbers, and other custom-generated local codes, which can neither provide certainty of uniqueness nor be ubiquitously recognizable across multiple systems and products.

The drawbacks of the existing systems are the lack of scalability and cost of manual intervention, alongside human errors, caused both, due to, lack of a standardized data transfer protocol as well as standardized data and user identification protocol.

In view of the above, there is a need of a system and a method which overcomes the above mentioned drawbacks.

Summary of the Invention
Accordingly, the present invention provides a method of capturing, processing and authenticating user information over a plurality of nodes in a network wherein each of the plurality of nodes operate on at least one protocol. The method comprising the steps of receiving the user information from one of the plurality of nodes, identifying to check whether the at least one protocol on which the node operates is a standardized protocol, converting the identified protocol to a standardized protocol, storing the user information in the standardized protocol based on a data structure inherent to the standardized protocol; and transferring the stored user information to a real-time authenticator for authenticating the user information.

In an embodiment the present invention provides a system for capturing, processing and authenticating user information over a plurality of nodes in a network wherein each of the plurality of nodes operate on at least one protocol. The system including a server having means to receive user information from at least one of the plurality of nodes; a processor for identifying to check whether the at least one protocol on which the node operates is a standardized protocol, a protocol converter for converting an identified protocol to a standardized protocol, a second database for storing the user information in the standardized protocol based on a data structure inherent to the standardized protocol and a real-time authenticator for verifying the stored user information wherein the identified protocol is synchronized with the standardized protocol for verifying the user information with a pre-stored data in a first database to authenticate the user if the user information matches with the pre-stored data.

Brief Description of the drawings
Reference will be made to embodiments of the invention, examples of which may be illustrated in the accompanying figures. These figures are intended to be illustrative, not limiting. Although the invention is generally described in the context of these embodiments, it should be understood that it is not intended to limit the scope of the invention to these particular embodiments.
Fig. 1 is a system for capturing, processing and authenticating user information over a plurality of nodes in a network wherein each of the plurality of nodes operate on at least one protocol.
Fig. 2 is a flowchart for a method of capturing, processing and authenticating user information over a plurality of nodes in a network wherein each of the plurality of nodes operate on at least one protocol


Brief description of the present invention
While this invention is susceptible of embodiments in many different forms, there is shown in the drawings and will herein be described in detail, a preferred embodiment of the invention with the understanding that the present disclosure is to be considered as an exemplification of the principles of the invention and is not intended to limit the broad aspects of the invention to the particular embodiment illustrated.
The subject matter is now described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the claimed subject matter. It may be evident however, that such matter can be practiced without these specific details. In other instances, well-known structures are shown in diagram form in order to facilitate describing the invention.
In an embodiment, the present invention provides standardization of data records transfers between the various linked APIs.
With reference to figure 1 of an embodiment of the invention, a system 100 for facilitating interaction between users operating on separate protocols over a network interface is illustrated. System 100 includes at least one user 110, a server 120 having a processor 121, a second database 122, a real time authenticator 123, a protocol converter 130 and an interface accessing a first database 140.
In an embodiment of the invention, user 110 provides an object related data and other details by means 112 of mobile phone, desktop, laptop or any other input/output devices.
The server 120 has means to receive user information from at least one of the plurality of nodes. The processor 121 configured for identifying to check whether the at least one protocol on which the node operates is a standardized protocol.

The protocol converter 130 converts an identified protocol to a standardized protocol. The second database 122 stores the user information in the standardized protocol based on a data structure inherent to the standardized protocol.

The real-time authenticator 123 verifies the stored user information wherein the identified protocol is synchronized with the standardized protocol for verifying the user information with a pre-stored data in a first database to authenticate the user if the user information matches with the pre-stored data.

Server 120 is configured for directing data flow in the network.

In an embodiment, protocol converter 130 converts identified protocol to standardized protocol. If user information received from one of the node where the node operates on more than one protocol, then the protocol converter has intelligence to identify the separate protocols and perform conversion accordingly.
In an embodiment of the invention, user 110 provides input including details of the like unique identification number (UID), mobile number, first name, last name, gender, age, address, pin-code etc.
With reference to Fig. 2 a method 200 of capturing, processing and authenticating user information over a plurality of nodes in a network is provided in accordance with an embodiment of the invention. The method provides for each of the plurality of nodes operating on at least one protocol. The method comprising the steps of S201 receiving the user information from one of the plurality of nodes, S202 processing the received user information for identifying to check whether the at least one protocol on which one of the plurality of nodes operates is a standardized protocol, S203 converting the identified protocol to a standardized protocol, S204 storing the user information in the standardized protocol based on a data structure inherent to the standardized protocol and S205 transferring the stored user information to a real-time authenticator for authenticating the user information.

In an embodiment, the identified protocol is synchronized with the standardized protocol for verifying the user information with a pre-stored data in a first database to authenticate the user if the user information matches with the pre-stored data.

In an embodiment the method further comprises the step S206 storing the user information in a second database if the user information does not match with the pre-stored data in the first database.

In an embodiment each of the plurality of nodes operates on a different protocol unique to them.
In an embodiment the method includes the step S207 capturing user information from the input provided by a user.

In an embodiment, the input is provided when selecting an object available on one of the plurality of nodes.

In an embodiment the object is a product available on an ecommerce platform.

In an embodiment, the user requests for a transaction, rebate, remittance, etc.

In an embodiment the authentication of the user information is performed by checking if mobile number of the user is valid. If the number is valid a one time password (OTP) is generated at the authentication server. The real time authenticator then sends OTP to the user and the server. The other details of the user information (UID, first name, last name, etc) are checked to be valid. If the other details of the user match with the pre-stored data of the first database, a signal is sent to the server for authenticating and authorizing access to the user. If the other details of the user do not match, then a signal is sent to the server for storing the user information in a second database.
In another embodiment, the present invention also comprises an adaptive intelligence record mapper that progressively improves quality of record mapping. It does so by mapping two record identifiers by the name, format, and metadata of both the record identifiers as well as the records themselves, obtained by either requesting or receiving the databases from the systems that are front-ended, or via a voluntary sample or real database sharing by the databases via an interface. Thus, as more interfaces link to the system, the system becomes more scalable and automated.
In another embodiment, the present invention leverages unique identification of data records as well as data record owners, transmission and reception to provide authenticity by preventing duplicate records and efforts.
In an embodiment the present invention provides a system that is capable of both authentication of data and data transmission and reception and systems thereof, as well as execution of authorized transactions between participating entities via their interfaces.
The basic concept of our invention comprises a standardized and user and data record authentication ready system multiple interfaces interacting with each other, to authenticate as well as transmit and receive data records in own formats. The system uses intelligence to convert multiple formats of data records and meta data records into a single standardized data record structure. This enables accurate data receipt, data storage and data retrieval.
Authentication of data transmission is a new and critical element of a successful standardization, as it ensures sanity of data by authenticating the transmitter of data into the system.
In an advantageous aspect, the present invention enables enterprises and individuals both to communicate data as well as metadata about themselves, as there is correlation of data fields between interfaces.
In the foregoing detailed description of embodiments of the invention, various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the embodiments of the invention require more features than are expressly recited.
It is understood that the above description is intended to be illustrative, and not restrictive. It is intended to cover all alternatives, modifications and equivalents as may be included within the spirit and scope of the invention. Many other embodiments will be apparent to those of skill in the art upon reviewing the above description.
,CLAIMS:1. A method of capturing, processing and authenticating user information over a plurality of nodes in a network wherein each of the plurality of nodes operate on at least one protocol, the method comprising the steps of:
receiving the user information from one of the plurality of nodes;
processing the received user information for identifying to check whether the at least one protocol on which one of the plurality of nodes operates is a standardized protocol;
converting the identified protocol to a standardized protocol;
storing the user information in the standardized protocol based on a data structure inherent to the standardized protocol; and
transferring the stored user information to a real-time authenticator for authenticating the user information.

2. The method as claimed in claim 1 wherein the identified protocol is synchronized with the standardized protocol for verifying the user information with a pre-stored data in a first database to authenticate the user if the user information matches with the pre-stored data.

3. The method as claimed in claim 2 further comprising the step of storing the user information in a second database if the user information does not match with the pre-stored data in the first database.

4. The method as claimed in claim 1 wherein each of the plurality of nodes operates on a different protocol unique to them.

5. The method as claimed in claim 1 wherein further comprising the step of capturing user information from the input provided by a user.

6. The method as claimed in claim 5 wherein the input is provided when selecting an object available on one of the plurality of nodes.

7. The method as claimed in claim 6 wherein the object is a product available on an ecommerce platform.

8. A system for capturing, processing and authenticating user information over a plurality of nodes in a network wherein each of the plurality of nodes operate on at least one protocol, the system comprising:
a server configured to processing and authenticating user information receive user information from at least one of the plurality of nodes;
a processor configured for identifying to check whether the at least one protocol on which the node operates is a standardized protocol;
a protocol converter for converting an identified protocol to a standardized protocol;
a second database for storing the user information in the standardized protocol based on a data structure inherent to the standardized protocol; and
a real-time authenticator for authenticating the user information.

9. The system as claimed in claim 8 wherein the identified protocol is synchronized with the standardized protocol for verifying the user information with a pre-stored data in a first database to authenticate the user if the user information matches with the pre-stored data.
10. The system as claimed in claim 8 wherein system uses intelligence to convert multiple formats of data records and meta data records into a single standardized data record structure to enable accurate data receipt, data storage and data retrieval.

11. The system as claimed in claim 8 wherein the first database is accessed by the server through an API for verifying the user information received from the user.

Documents

Orders

Section Controller Decision Date

Application Documents

# Name Date
1 3398-MUM-2013-Correspondence to notify the Controller [04-03-2024(online)].pdf 2024-03-04
1 Form 5 (28-10-2014).pdf 2014-10-28
2 Complete Specification & Drawings on Form 2 (28-10-2014).pdf 2014-10-28
2 3398-MUM-2013-US(14)-HearingNotice-(HearingDate-07-03-2024).pdf 2024-02-13
3 3398-MUM-2013-Response to office action [19-10-2022(online)].pdf 2022-10-19
3 3398-MUM-2013-FORM 18 [26-10-2017(online)].pdf 2017-10-26
4 Provisional specification-Srikanth.pdf 2018-08-11
4 3398-MUM-2013-FER.pdf 2021-10-03
5 Form-2(Online).pdf 2018-08-11
5 3398-MUM-2013-ABSTRACT [28-05-2021(online)].pdf 2021-05-28
6 FORM 5.pdf 2018-08-11
6 3398-MUM-2013-CLAIMS [28-05-2021(online)].pdf 2021-05-28
7 FORM 3.pdf 2018-08-11
7 3398-MUM-2013-COMPLETE SPECIFICATION [28-05-2021(online)].pdf 2021-05-28
8 Drawings shrikanth.pdf 2018-08-11
8 3398-MUM-2013-DRAWING [28-05-2021(online)].pdf 2021-05-28
9 ABSTRACT.jpg 2018-08-11
9 3398-MUM-2013-FER_SER_REPLY [28-05-2021(online)].pdf 2021-05-28
10 3398-MUM-2013-OTHERS [28-05-2021(online)].pdf 2021-05-28
10 3398-MUM-2013-POWER OF ATTORNEY(2-12-2013).pdf 2018-08-11
11 3398-MUM-2013-FORM 1(2-12-2013).pdf 2018-08-11
11 3398-MUM-2013-FORM 4(ii) [25-02-2021(online)].pdf 2021-02-25
12 3398-MUM-2013-CORRESPONDENCE(2-12-2013).pdf 2018-08-11
13 3398-MUM-2013-FORM 1(2-12-2013).pdf 2018-08-11
13 3398-MUM-2013-FORM 4(ii) [25-02-2021(online)].pdf 2021-02-25
14 3398-MUM-2013-OTHERS [28-05-2021(online)].pdf 2021-05-28
14 3398-MUM-2013-POWER OF ATTORNEY(2-12-2013).pdf 2018-08-11
15 3398-MUM-2013-FER_SER_REPLY [28-05-2021(online)].pdf 2021-05-28
15 ABSTRACT.jpg 2018-08-11
16 3398-MUM-2013-DRAWING [28-05-2021(online)].pdf 2021-05-28
16 Drawings shrikanth.pdf 2018-08-11
17 3398-MUM-2013-COMPLETE SPECIFICATION [28-05-2021(online)].pdf 2021-05-28
17 FORM 3.pdf 2018-08-11
18 3398-MUM-2013-CLAIMS [28-05-2021(online)].pdf 2021-05-28
18 FORM 5.pdf 2018-08-11
19 3398-MUM-2013-ABSTRACT [28-05-2021(online)].pdf 2021-05-28
19 Form-2(Online).pdf 2018-08-11
20 Provisional specification-Srikanth.pdf 2018-08-11
20 3398-MUM-2013-FER.pdf 2021-10-03
21 3398-MUM-2013-Response to office action [19-10-2022(online)].pdf 2022-10-19
21 3398-MUM-2013-FORM 18 [26-10-2017(online)].pdf 2017-10-26
22 Complete Specification & Drawings on Form 2 (28-10-2014).pdf 2014-10-28
22 3398-MUM-2013-US(14)-HearingNotice-(HearingDate-07-03-2024).pdf 2024-02-13
23 Form 5 (28-10-2014).pdf 2014-10-28
23 3398-MUM-2013-Correspondence to notify the Controller [04-03-2024(online)].pdf 2024-03-04

Search Strategy

1 serachstrategy_2020-02-2713-14-35_27-02-2020.pdf