Sign In to Follow Application
View All Documents & Correspondence

Method And System For Processing Data In An Internet Of Things (Iot) Environment

Abstract: A method, corresponding system, and computer program product for edge data processing in an Internet of Things (IoT) environment is disclosed. The method includes receiving, by an IoT Gateway device, a data traffic generated by one or more edge devices in the IoT environment. Thereafter, the IoT Gateway device classifies the received data traffic as one of a normal data and a critical data. In response to classifying the received data traffic, the IoT Gateway device thereafter automatically designates a network location for processing the received data traffic. The network location corresponds to an edge computing resource arranged locally to the IoT Gateway device when the received data is classified as critical data and the network location corresponds to a remote cloud computing resource when the received data is classified as normal data. FIG.1

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
05 July 2017
Publication Number
02/2019
Publication Type
INA
Invention Field
COMMUNICATION
Status
Email
bangalore@knspartners.com
Parent Application
Patent Number
Legal Status
Grant Date
2023-05-19
Renewal Date

Applicants

WIPRO LIMITED
Doddakannelli, Sarjapur Road, Bangalore 560035, Karnataka, India.

Inventors

1. RADHA KRISHNA SINGURU
Flat# 206, Daffodil, Bhanu Township, Hafeezpet, Miyapur, Hyderabad, Telengana- 500050, India.

Specification

Claims:WE CLAIM:
1. A method for edge data processing in an Internet of Things (IoT) environment, the method comprising:
receiving, by an IoT Gateway device, a data traffic generated by at least one edge device in the IoT environment;
classifying, by the IoT Gateway device, the received data traffic as one of a normal data and a critical data; and
automatically designating, by the IoT Gateway device, a network location for processing the received data traffic in response to classifying, wherein the network location corresponds to an edge computing resource arranged locally to the IoT Gateway device when the received data is classified as critical data and the network location corresponds to a remote cloud computing resource when the received data is classified as normal data.

2. The method of claim 1, wherein the received data traffic is classified as critical data or normal data based on determining a time criticalness level of the received data traffic, wherein the time criticalness level is determined by comparing the received data traffic with a training data associated with time criticalness attributes.

3. The method of claim 2, wherein the time criticalness attributes are determined based on at least one of domain knowledge, application specific features, service quality attributes, existing network resource capabilities, temporal characteristics, tenant preferences, deployment considerations, user characteristics, and historical attributes.

4. The method of claim 1, wherein the received data is classified as critical data or normal data based on determining a confidentiality level of the received data traffic, wherein the confidentiality level is determined by comparing the received data traffic with a training data associated with confidentiality attributes.

5. The method of claim 4, wherein the confidentiality attributes are determined based on at least one of an application type, deployment considerations, legal restrictions, financial data protection requirements, data privacy requirements, and regulatory policies.

6. The method of claim 1, further comprising automatically creating at least one container instance for handling processing tasks associated with the critical data in the edge computing resource, wherein the at least one container instance is created based on inputs received from the IoT Gateway device.

7. The method of claim 6, further comprising automatically scaling up and down the at least one container instance for handling the processing tasks based on a load factor associated with the received critical data traffic.

8. The method of claim 1, further comprising automatically diverting the received normal data traffic to the remote cloud computing resource for handling the processing tasks associated with the normal data.

9. The method of claim 1, wherein the received data traffic is classified as normal data or critical data by using at least one of a machine learning algorithm, and an artificial intelligence algorithm.

10. A system for edge data processing in an Internet of Things (IoT) environment, the system comprising:
a cloud server;
at least one edge device; and
an IoT Gateway device, wherein the IoT Gateway device is operatively coupled with the at least one edge device and the cloud server, the IoT Gateway device configured to:
receive a data traffic generated by at least one edge device in the IoT environment;
classify the received data traffic as one of a normal data and a critical data; and
automatically designate a network location for processing the received data traffic in response to classifying, wherein the network location corresponds to an edge computing resource arranged locally to the IoT Gateway device when the received data is classified as critical data and the network location corresponds to a remote cloud computing resource when the received data is classified as normal data.

11. The system of claim 10, wherein the IoT Gateway device is further configured to classify the received data traffic as critical data or normal data based on determining a time criticalness level of the received data traffic, wherein the time criticalness level is determined by comparing the received data traffic with a training data associated with time criticalness attributes.

12. The system of claim 11, wherein the IoT Gateway device is further configured to determine the time criticalness attributes based on at least one of a domain knowledge, application specific features, service quality attributes, existing network resource capabilities, temporal characteristics, user characteristics, and historical attributes.

13. The system of claim 10, wherein the IoT Gateway device is further configured to classify the received data traffic as critical data or normal data based on determining a confidentiality level of the received data traffic, wherein the confidentiality level is determined by comparing the received data traffic with a training data associated with confidentiality attributes.

14. The system of claim 13, wherein the IoT Gateway device is further configured to determine the confidentiality attributes based on at least one of an application type, deployment considerations, legal restrictions, financial data protection requirements, data privacy requirements, and regulatory policies.

15. The system of claim 10, wherein the IoT Gateway device is further configured to automatically create at least one container instance for handling processing tasks associated with the critical data in the edge computing resource, wherein the at least one container instance is created based on inputs received from the IoT Gateway device.

16. The system of claim 15, wherein the IoT Gateway device is further configured to employ a container orchestrator arranged locally to the IoT Gateway device for creating the at least one container instance.

17. The system of claim 16, wherein the IoT Gateway device is further configured to automatically scale up and down the at least one container instance for handling processing tasks based on a load factor associated with the received critical data traffic.

18. The system of claim 10, wherein the IoT Gateway device is further configured to automatically divert the received normal data traffic to the remote cloud computing resource for handling the processing tasks associated with the normal data.

19. The system of claim 10, wherein the IoT Gateway device is further configured to employ at least one of a machine learning algorithm, and an artificial intelligence algorithm for classifying the received data traffic as normal data and critical data.

Dated this 5th day of July, 2017

R Ramya Rao
Of K&S Partners
Agent for the Applicant
, Description:TECHNICAL FIELD
The present invention relates to an Internet of Things (IoT) environment, in particular, to method and system for processing data in an IoT environment.

Documents

Application Documents

# Name Date
1 Power of Attorney [05-07-2017(online)].pdf 2017-07-05
2 Form 5 [05-07-2017(online)].pdf 2017-07-05
3 Form 3 [05-07-2017(online)].pdf 2017-07-05
4 Form 18 [05-07-2017(online)].pdf_83.pdf 2017-07-05
5 Form 18 [05-07-2017(online)].pdf 2017-07-05
6 Form 1 [05-07-2017(online)].pdf 2017-07-05
7 Drawing [05-07-2017(online)].pdf 2017-07-05
8 Description(Complete) [05-07-2017(online)].pdf_84.pdf 2017-07-05
9 Description(Complete) [05-07-2017(online)].pdf 2017-07-05
10 REQUEST FOR CERTIFIED COPY [06-07-2017(online)].pdf 2017-07-06
11 201741023647-Proof of Right (MANDATORY) [01-09-2017(online)].pdf 2017-09-01
12 Correspondence By Agent_form30,Form1_05-09-2017.pdf 2017-09-05
13 201741023647-REQUEST FOR CERTIFIED COPY [20-12-2017(online)].pdf 2017-12-20
14 201741023647-REQUEST FOR CERTIFIED COPY [07-02-2018(online)].pdf 2018-02-07
15 201741023647-FER.pdf 2020-06-25
16 201741023647-RELEVANT DOCUMENTS [08-12-2020(online)].pdf 2020-12-08
17 201741023647-PETITION UNDER RULE 137 [08-12-2020(online)].pdf 2020-12-08
18 201741023647-OTHERS [08-12-2020(online)].pdf 2020-12-08
19 201741023647-Information under section 8(2) [08-12-2020(online)].pdf 2020-12-08
20 201741023647-FORM 3 [08-12-2020(online)].pdf 2020-12-08
21 201741023647-FER_SER_REPLY [08-12-2020(online)].pdf 2020-12-08
22 201741023647-DRAWING [08-12-2020(online)].pdf 2020-12-08
23 201741023647-CORRESPONDENCE [08-12-2020(online)].pdf 2020-12-08
24 201741023647-CLAIMS [08-12-2020(online)].pdf 2020-12-08
25 201741023647-PatentCertificate19-05-2023.pdf 2023-05-19
26 201741023647-IntimationOfGrant19-05-2023.pdf 2023-05-19
27 201741023647-PROOF OF ALTERATION [16-08-2023(online)].pdf 2023-08-16

Search Strategy

1 SearchStrategyE_24-06-2020.pdf

ERegister / Renewals

3rd: 02 Aug 2023

From 05/07/2019 - To 05/07/2020

4th: 02 Aug 2023

From 05/07/2020 - To 05/07/2021

5th: 02 Aug 2023

From 05/07/2021 - To 05/07/2022

6th: 02 Aug 2023

From 05/07/2022 - To 05/07/2023

7th: 02 Aug 2023

From 05/07/2023 - To 05/07/2024

8th: 01 Jul 2024

From 05/07/2024 - To 05/07/2025

9th: 01 Jul 2025

From 05/07/2025 - To 05/07/2026