[go: up one dir, main page]

US12088665B2 - Data replication processing method between management modules in rugged environment - Google Patents

Data replication processing method between management modules in rugged environment Download PDF

Info

Publication number
US12088665B2
US12088665B2 US17/497,183 US202117497183A US12088665B2 US 12088665 B2 US12088665 B2 US 12088665B2 US 202117497183 A US202117497183 A US 202117497183A US 12088665 B2 US12088665 B2 US 12088665B2
Authority
US
United States
Prior art keywords
management device
management
storing
edge server
edge
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
US17/497,183
Other versions
US20220150304A1 (en
Inventor
Jae Hoon An
Young Hwan Kim
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Korea Electronics Technology Institute
Original Assignee
Korea Electronics Technology Institute
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Korea Electronics Technology Institute filed Critical Korea Electronics Technology Institute
Assigned to KOREA ELECTRONICS TECHNOLOGY INSTITUTE reassignment KOREA ELECTRONICS TECHNOLOGY INSTITUTE ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: AN, JAE HOON, KIM, YOUNG HWAN
Publication of US20220150304A1 publication Critical patent/US20220150304A1/en
Application granted granted Critical
Publication of US12088665B2 publication Critical patent/US12088665B2/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/1608—Error detection by comparing the output signals of redundant hardware
    • G06F11/1612—Error detection by comparing the output signals of redundant hardware where the redundant component is persistent storage
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/1666—Error detection or correction of the data by redundancy in hardware where the redundant component is memory or memory area
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/2053—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant
    • G06F11/2056—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/2053—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant
    • G06F11/2056—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring
    • G06F11/2071—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring using a plurality of controllers
    • G06F11/2076—Synchronous techniques
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3058—Monitoring arrangements for monitoring environmental properties or parameters of the computing system or of the computing system component, e.g. monitoring of power, currents, temperature, humidity, position, vibrations
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5072—Grid computing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/2053—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant
    • G06F11/2094—Redundant storage or storage space
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/2097—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements maintaining the standby controller/processing unit updated
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/86—Event-based monitoring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters

Definitions

  • the present disclosure relates generally to edge service management technology, and more particularly, to replication technology of an edge management means in providing an edge service in a rugged environment.
  • an edge server management module replication method includes: a step of collecting, by a first management module, environment information of an edge server; a step of managing, by the first management module, the edge server, based on the collected environmental information; a first storage step of storing, by the first management module, management data related to the edge server in a repository of the first management module; and a second storage step of storing, by a second management module, the management data stored at the first storage step in a repository of the second management module.
  • the second storage step may be performed at the same time as the first storage step.
  • the second storage step may include, when an event related to management data storage occurs at the first management module, capturing the occurring event and storing the management data.
  • the first management module and the second management module may synchronize the occurring event with each other.
  • the event may be a write system call in the first management module.
  • the second storage step may be performed at the same time as the first storage step when an external environment of the edge server is in a first state.
  • the second storage step may be performed according to a defined period when the external environment of the edge server is in a second state.
  • the edge server management module replication method may further include: a step of understanding, by the second management module, a state of the first management module; a step of collecting, by the second management module, environment information of the edge server when it is understood that the first management module is in a disabled state; and a step of managing, by the second management module, the edge server, based on the collected environmental information.
  • An environment of the edge server may be a rugged environment.
  • an edge server management module includes: a first management module configured to collect environmental information of an edge server and to manage the edge server, based on the collected environmental information, and to store management data related to the edge server in a repository of the first management module; and a second management module configured to store the management data stored in the first management module in a repository of the second management module.
  • an edge server management module replication method includes: a first storage step of storing, by a first management module, management data related to an edge server in a repository of the first management module; and a second storage step of storing, by a second management module, the management data stored at the first storage step in a repository of the second management module.
  • an edge server system includes: an edge server configured to provide an edge service; a first management module configured to collect environmental information of the edge server and to manage the edge server, based on the collected environmental information, and to store management data related to the edge server in a repository of the first management module; and a second management module configured to store the management data stored in the first management module in a repository of the second management module.
  • the time required to respond to an error occurring in a severe industrial site can be minimized through data replication processing between replicated edge management modules in a rugged environment, so that a continuous edge service can be provided without interruption.
  • FIG. 1 is a view illustrating an edge server system to which the present disclosure is applicable
  • FIG. 2 is a view illustrating a concept of state monitoring and mode switching processes between replicated edge management modules
  • FIG. 3 is a view illustrating a process of performing data replication by copying data between edge management modules
  • FIG. 4 is a view schematically illustrating a concept of data replication (mirroring) based on an event between edge management modules;
  • FIG. 5 is a detailed block diagram of an edge management module shown in FIG. 1 .
  • an edge management module is replicated as a solution for preventing loss of management data.
  • embodiments of the present disclosure suggest a solution for replicating management data in real time by replicated edge server management modules storing the management data simultaneously.
  • FIG. 1 is a view illustrating an edge server system to which the present disclosure is applicable.
  • the edge server system to which the present disclosure is applicable includes an edge server 110 , an edge management module 120 , a sensor 130 , a fan 140 , and a heater 150 .
  • the edge server 110 is a server that is allocated resources to provide an edge service and performs edge computing. Since the edge server 110 is generated for every edge service, a plurality of edge servers may be generated.
  • the edge management module 120 is a module for managing and controlling the edge server 110 . When necessary, the edge management module 120 may be positioned outside the edge server system.
  • a Redfish interface may be applied as an interface for connecting/managing/controlling the edge management module 120 and the edge server 110 .
  • the sensor 130 is configured to collect environmental information (temperature, humidity, dusts, etc.) of the edge server system, and the fan 140 and the heater 150 are configured to control temperature of the edge server system.
  • the edge management module 120 includes two replicated edge management modules 120 - 1 , 120 - 2 . Accordingly, one of the edge management modules 120 - 1 , 120 - 2 operates in an active mode to collect environmental information of the edge server system and to manages the edge server system, based on the collected environmental information.
  • the other one of the edge management modules 120 - 1 , 120 - 2 operates in a passive mode to copy data of the edge management module operating in the active mode and to monitor a state.
  • FIG. 2 illustrates a concept of state monitoring and mode switching processes between the replicated edge management modules 120 - 1 , 120 - 2 .
  • the edge management modules 120 - 1 , 120 - 2 may understand each other's states by checking a heartbeat, and, when it is understood that the edge management module operating in the active mode is in a disabled state, the edge management module operating in the passive mode may be switched to the active mode, and may collect environmental information of the edge service system and may manage the edge server system.
  • the edge management module operating in the passive mode replicates data by copying data of the edge management module operating in the active mode. This process is illustrated in FIG. 3 .
  • edge management module # 1 120 - 1 operates in the active mode and the edge management module # 2 120 - 2 operates in the passive mode.
  • the edge management module # 1 120 - 1 stores management data that is generated in managing the edge server system in its repository.
  • the edge management module # 2 120 - 2 mirrors the corresponding management data and stores the same in its repository.
  • the edge management module # 2 120 - 2 stores the management data at the same time as the edge management module # 1 120 - 1 stores the management data.
  • the edge management modules 120 - 1 , 120 - 2 are provided with event synchronization modules 125 - 1 , 125 - 2 .
  • the event synchronization module 125 - 1 , 125 - 2 is a module for synchronizing an event occurring at the edge management module 120 - 1 , 120 - 2 .
  • the event synchronization module 125 - 1 captures the occurring event and transmits the event to the edge management module # 2 120 - 2 , such that the same management data is stored in the repository of the edge management module # 2 120 - 2 at the same time.
  • FIG. 4 schematically illustrates a concept of event-based data replication (mirroring) between the edge management module # 1 120 - 1 and the edge management module # 2 120 - 2 .
  • an event related to data storage that occurs at any one of the edge management modules 120 - 1 , 120 - 2 is transmitted to the other one in real time, and accordingly, it is identified that data is copied by capturing the event in real time.
  • the data storage-related event may be a write system call.
  • the replication by the edge management modules 120 - 1 , 120 - 2 themselves and the real-time replication of the management data can minimize a response time without data loss when there is a problem in the edge service in the rugged environment, and can enhance a fault tolerance function.
  • additional data verification model and step are not required due to the real-time data synchronization.
  • FIG. 5 is a detailed block diagram of the edge management module 120 - 1 , 120 - 2 .
  • the edge management module includes a server interface 121 , a processor 122 , a peripheral device interface 122 , and a memory 124 .
  • the server interface 121 is an interface for communication connection and data communication with the edge server 110
  • the peripheral device interface 124 is an interface for communication connection and data communication with the sensor 130 , the fan 140 , and the heater 150 .
  • the processor 122 performs functions necessary for controlling/managing the edge server system, suggested in FIGS. 2 , 3 , and 4 , in particular, for monitoring a state, switching a mode, and replicating data.
  • the memory 123 provides a storage space necessary for the processor 1220 to perform corresponding functions.
  • real-time data replication may be performed. That is, only in the corresponding state, the passive edge management module simultaneously stores management data that is generated at the active edge management module in response to a storage event.
  • the passive edge management module may replicate data by mirroring management data generated at the active edge management module intermittently according to a defined period.
  • Embodiments of the present disclosure suggest a real-time data replication method in a standard-based edge computing management module for providing a computing-intensive edge service in a poor environment.
  • the replication configuration considering a fault tolerance operation in a rugged environment can minimize the time required to respond to an error, does not cause loss of data through event-based data synchronization in the replicated management module when an error occurs, and can reduce a data verification step for continuous integrated management through a simultaneous storing method.
  • the technical concept of the present disclosure may be applied to a computer-readable recording medium which records a computer program for performing the functions of the apparatus and the method according to the present embodiments.
  • the technical idea according to various embodiments of the present disclosure may be implemented in the form of a computer readable code recorded on the computer-readable recording medium.
  • the computer-readable recording medium may be any data storage device that can be read by a computer and can store data.
  • the computer-readable recording medium may be a read only memory (ROM), a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical disk, a hard disk drive, or the like.
  • a computer readable code or program that is stored in the computer readable recording medium may be transmitted via a network connected between computers.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Computing Systems (AREA)
  • Software Systems (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Mathematical Physics (AREA)
  • Hardware Redundancy (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

There is provided a method of data replication between management modules in a rugged environment. According to an embodiment of the present disclosure, an edge server management module replication method includes: a step of collecting, by a first management module, environment information of an edge server; a step of managing, by the first management module, the edge server, based on the collected environmental information; a first storage step of storing, by the first management module, management data related to the edge server in a repository of the first management module; and a second storage step of storing, by a second management module, the management data stored at the first storage step in a repository of the second management module. Accordingly, the time required to respond to an error occurring in a severe industrial site can be minimized through data replication processing between replicated edge management modules in a rugged environment, so that a continuous edge service can be provided without interruption.

Description

PRIORITY
This application is based on and claims priority under 35 U.S.C. § 119 to Korean Patent Application No. 10-2020-0147256, filed on Nov. 6, 2020, in the Korean Intellectual Property Office, the disclosure of which is herein incorporated by reference in its entirety.
BACKGROUND Field
The present disclosure relates generally to edge service management technology, and more particularly, to replication technology of an edge management means in providing an edge service in a rugged environment.
Description of Related Art
In a rugged environment (severe environment), IT equipment is difficult to operate normally, and management and control therefor is more highlighted. However, current technology for overcoming the rugged environment only focuses on hardware-level approach for reinforcing/supplementing an exterior of IT equipment.
However, abnormal climate conditions which are becoming serious recently make it more difficult to respond with only the above-described approach. Accordingly, there is a need for a method for responding to a rugged environment from a different viewpoint.
In particular, since loss of management data in a rugged environment results in loss of control authority of an available computing module, continuous data management is more essential.
SUMMARY
To address the above-discussed deficiencies of the prior art, it is a primary object of the present disclosure to provide a data replication processing method between edge management modules in a rugged environment, as a solution for providing a continuous edge service without interruption in a severe industrial site.
According to an embodiment of the present disclosure to achieve the above-described object, an edge server management module replication method includes: a step of collecting, by a first management module, environment information of an edge server; a step of managing, by the first management module, the edge server, based on the collected environmental information; a first storage step of storing, by the first management module, management data related to the edge server in a repository of the first management module; and a second storage step of storing, by a second management module, the management data stored at the first storage step in a repository of the second management module.
The second storage step may be performed at the same time as the first storage step.
The second storage step may include, when an event related to management data storage occurs at the first management module, capturing the occurring event and storing the management data.
The first management module and the second management module may synchronize the occurring event with each other.
The event may be a write system call in the first management module.
The second storage step may be performed at the same time as the first storage step when an external environment of the edge server is in a first state.
The second storage step may be performed according to a defined period when the external environment of the edge server is in a second state.
The edge server management module replication method according to an embodiment of the disclosure may further include: a step of understanding, by the second management module, a state of the first management module; a step of collecting, by the second management module, environment information of the edge server when it is understood that the first management module is in a disabled state; and a step of managing, by the second management module, the edge server, based on the collected environmental information.
An environment of the edge server may be a rugged environment.
According to another embodiment of the present disclosure, an edge server management module includes: a first management module configured to collect environmental information of an edge server and to manage the edge server, based on the collected environmental information, and to store management data related to the edge server in a repository of the first management module; and a second management module configured to store the management data stored in the first management module in a repository of the second management module.
According to still another embodiment of the present disclosure, an edge server management module replication method includes: a first storage step of storing, by a first management module, management data related to an edge server in a repository of the first management module; and a second storage step of storing, by a second management module, the management data stored at the first storage step in a repository of the second management module.
According to yet another embodiment of the present disclosure, an edge server system includes: an edge server configured to provide an edge service; a first management module configured to collect environmental information of the edge server and to manage the edge server, based on the collected environmental information, and to store management data related to the edge server in a repository of the first management module; and a second management module configured to store the management data stored in the first management module in a repository of the second management module.
According to embodiments of the present disclosure described above, the time required to respond to an error occurring in a severe industrial site can be minimized through data replication processing between replicated edge management modules in a rugged environment, so that a continuous edge service can be provided without interruption.
Other aspects, advantages, and salient features of the invention will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses exemplary embodiments of the invention.
Before undertaking the DETAILED DESCRIPTION OF THE INVENTION below, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document: the terms “include” and “comprise,” as well as derivatives thereof, mean inclusion without limitation; the term “or,” is inclusive, meaning and/or; the phrases “associated with” and “associated therewith,” as well as derivatives thereof, may mean to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, or the like. Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.
BRIEF DESCRIPTION OF THE DRAWINGS
For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which like reference numerals represent like parts:
FIG. 1 is a view illustrating an edge server system to which the present disclosure is applicable;
FIG. 2 is a view illustrating a concept of state monitoring and mode switching processes between replicated edge management modules;
FIG. 3 is a view illustrating a process of performing data replication by copying data between edge management modules;
FIG. 4 is a view schematically illustrating a concept of data replication (mirroring) based on an event between edge management modules; and
FIG. 5 is a detailed block diagram of an edge management module shown in FIG. 1 .
 DETAILED DESCRIPTION
Hereinafter, the present disclosure will be described in detail with reference to the accompanying drawings.
In an embodiment of the present disclosure, a method for replicating an edge management module in a rugged environment and replicating management data through this is suggested.
In a rugged environment, for example, in a poor environment in which external temperature is high temperature of 63° C. or higher or is low temperature of −21° C. or lower, management of an edge server is more important to provide a computing-intensive edge service. Accordingly, in embodiments of the present disclosure, an edge management module is replicated as a solution for preventing loss of management data.
In addition, embodiments of the present disclosure suggest a solution for replicating management data in real time by replicated edge server management modules storing the management data simultaneously.
FIG. 1 is a view illustrating an edge server system to which the present disclosure is applicable. The edge server system to which the present disclosure is applicable includes an edge server 110, an edge management module 120, a sensor 130, a fan 140, and a heater 150.
The edge server 110 is a server that is allocated resources to provide an edge service and performs edge computing. Since the edge server 110 is generated for every edge service, a plurality of edge servers may be generated.
The edge management module 120 is a module for managing and controlling the edge server 110. When necessary, the edge management module 120 may be positioned outside the edge server system.
A Redfish interface (IF) may be applied as an interface for connecting/managing/controlling the edge management module 120 and the edge server 110.
The sensor 130 is configured to collect environmental information (temperature, humidity, dusts, etc.) of the edge server system, and the fan 140 and the heater 150 are configured to control temperature of the edge server system.
The edge management module 120 includes two replicated edge management modules 120-1, 120-2. Accordingly, one of the edge management modules 120-1, 120-2 operates in an active mode to collect environmental information of the edge server system and to manages the edge server system, based on the collected environmental information.
In addition, the other one of the edge management modules 120-1, 120-2 operates in a passive mode to copy data of the edge management module operating in the active mode and to monitor a state.
FIG. 2 illustrates a concept of state monitoring and mode switching processes between the replicated edge management modules 120-1, 120-2.
As shown in FIG. 2 , the edge management modules 120-1, 120-2 may understand each other's states by checking a heartbeat, and, when it is understood that the edge management module operating in the active mode is in a disabled state, the edge management module operating in the passive mode may be switched to the active mode, and may collect environmental information of the edge service system and may manage the edge server system.
On the other hand, the edge management module operating in the passive mode replicates data by copying data of the edge management module operating in the active mode. This process is illustrated in FIG. 3 .
In FIG. 3 , it is assumed that the edge management module # 1 120-1 operates in the active mode and the edge management module # 2 120-2 operates in the passive mode.
As shown in the drawing, the edge management module # 1 120-1 stores management data that is generated in managing the edge server system in its repository.
When the management data is stored by the edge management module # 1 120-1, the edge management module # 2 120-2 mirrors the corresponding management data and stores the same in its repository. In addition, the edge management module # 2 120-2 stores the management data at the same time as the edge management module # 1 120-1 stores the management data.
To achieve this, the edge management modules 120-1, 120-2 are provided with event synchronization modules 125-1, 125-2. The event synchronization module 125-1, 125-2 is a module for synchronizing an event occurring at the edge management module 120-1, 120-2.
Specifically, when an event related to management data storage occurs at the edge management module # 1 120-1 operating in the active mode, the event synchronization module 125-1 captures the occurring event and transmits the event to the edge management module # 2 120-2, such that the same management data is stored in the repository of the edge management module # 2 120-2 at the same time.
FIG. 4 schematically illustrates a concept of event-based data replication (mirroring) between the edge management module # 1 120-1 and the edge management module # 2 120-2. As shown in the drawing, an event related to data storage that occurs at any one of the edge management modules 120-1, 120-2 is transmitted to the other one in real time, and accordingly, it is identified that data is copied by capturing the event in real time. Herein, the data storage-related event may be a write system call.
The replication by the edge management modules 120-1, 120-2 themselves and the real-time replication of the management data can minimize a response time without data loss when there is a problem in the edge service in the rugged environment, and can enhance a fault tolerance function. In particular, there is an advantage that additional data verification model and step are not required due to the real-time data synchronization.
Hereinafter, detailed configurations of the edge management modules 120-1, 120-2 shown in FIG. 1 will be described with reference to FIG. 5 . Since the edge management modules 120-1, 120-2 are implemented by the same configuration, only one edge management module is illustrated. FIG. 5 is a detailed block diagram of the edge management module 120-1, 120-2.
As shown in the drawing, the edge management module includes a server interface 121, a processor 122, a peripheral device interface 122, and a memory 124.
The server interface 121 is an interface for communication connection and data communication with the edge server 110, and the peripheral device interface 124 is an interface for communication connection and data communication with the sensor 130, the fan 140, and the heater 150.
The processor 122 performs functions necessary for controlling/managing the edge server system, suggested in FIGS. 2, 3, and 4 , in particular, for monitoring a state, switching a mode, and replicating data.
The memory 123 provides a storage space necessary for the processor 1220 to perform corresponding functions.
Up to now, the method for processing data replication between the management modules in the rugged environment has been described with reference to preferred embodiments.
In the above-described embodiments, it is assumed that real-time data replication between the edge server management modules is performed at ordinary times, but this is merely an example. Changes can be made such that data replication is performed according to a condition.
For example, only when an external environment of the edge server system is in a serious danger state, real-time data replication may be performed. That is, only in the corresponding state, the passive edge management module simultaneously stores management data that is generated at the active edge management module in response to a storage event.
Otherwise, the passive edge management module may replicate data by mirroring management data generated at the active edge management module intermittently according to a defined period.
Embodiments of the present disclosure suggest a real-time data replication method in a standard-based edge computing management module for providing a computing-intensive edge service in a poor environment.
Through this, internal operations are processed so as to minimize the time required to detect a system error of the management module for integrally managing/controlling the edge service providing system, and to continuously manage based on synchronized data in real time through an event driven method.
The replication configuration considering a fault tolerance operation in a rugged environment can minimize the time required to respond to an error, does not cause loss of data through event-based data synchronization in the replicated management module when an error occurs, and can reduce a data verification step for continuous integrated management through a simultaneous storing method.
The technical concept of the present disclosure may be applied to a computer-readable recording medium which records a computer program for performing the functions of the apparatus and the method according to the present embodiments. In addition, the technical idea according to various embodiments of the present disclosure may be implemented in the form of a computer readable code recorded on the computer-readable recording medium. The computer-readable recording medium may be any data storage device that can be read by a computer and can store data. For example, the computer-readable recording medium may be a read only memory (ROM), a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical disk, a hard disk drive, or the like. A computer readable code or program that is stored in the computer readable recording medium may be transmitted via a network connected between computers.
In addition, while preferred embodiments of the present disclosure have been illustrated and described, the present disclosure is not limited to the above-described specific embodiments. Various changes can be made by a person skilled in the art without departing from the scope of the present disclosure claimed in claims, and also, changed embodiments should not be understood as being separate from the technical idea or prospect of the present disclosure.

Claims (11)

What is claimed is:
1. An edge server management replication method comprising:
collecting, by a first management device, environment information of an edge server;
controlling, by the first management device, a managing and an operating of the edge server, based on the collected environmental information;
performing, by the first management device, a first storing of management data related to the edge server in a repository of the first management device;
performing, by a second management device capable of managing and operating the edge server, a second storing of the management data, stored in a repository of the first management device at the performed first storing, in a repository of the second management device using a direct communication between the first management device and the second management device in response to the edge server being in a predefined state, wherein the second storing is performed using the direct communication between the first management device and the second management device at the same time as the first storing performed when an external environment of the edge server is in a first state, wherein the performing of the second storing comprises, when an event related to management data storage occurs at the first management device, capturing the occurring event and storing the management data, wherein the event is a write system call in the first management device; and
skipping data verification for continuous integrated management through a simultaneous storing when the second storing is performed by the second management device at the same time as the first storing performed.
2. The method of claim 1, wherein the first management device and the second management device are configured to synchronize the occurring event with each other.
3. The method of claim 1, wherein the second storing is performed according to a defined period when the external environment of the edge server is in a second state.
4. The method of claim 1, further comprising:
understanding, by the second management device, a state of the first management device; collecting, by the second management device, environment information of the edge server when it is understood that the first management device is in a disabled state; and managing, by the second management device, the edge server, based on the collected environmental information.
5. The method of claim 1, wherein an environment of the edge server is a rugged environment.
6. An edge server management system comprising:
a first management device configured to collect environmental information of an edge server and to manage and/or control an operation of the edge server, based on the collected environmental information, and to perform a first storing of management data related to the edge server in a repository of the first management device; and
a second management device configured to perform a second storing of the management data stored in the first management device in a repository of the second management device using a direct communication between the first management device and the second management device, in response to the edge server being in a predefined state, wherein the second storing is performed using the direct communication between the first management device and the second management device at the same time as the first storing performed when an external environment of the edge server is in a first state , wherein the performing of the second storing comprises, when an event related to management data storage occurs at the first management device, capturing the occurring event and storing the management data, wherein the event is a write system call in the first management device, and
skip a data verification for continuous integrated management through a simultaneous storing when the second storing is performed by the second management device at the same time as the first storing performed.
7. An edge server management replication method comprising:
performing, by a first management device, a first storing of management data related to an edge server in a repository of the first management device;
performing, by a second management device, a second storing the management data, stored in a repository of the first management device at the performed first storing, in a repository of the second management device using a direct communication between the first management device and the second management device in response to the edge server being in a predefined state, wherein the second storing is performed using the direct communication between the first management device and the second management device at the same time as the first storing performed when an external environment of the edge server is in a first state, wherein the performing of the second storing comprises, when an event related to management data storage occurs at the first management device, capturing the occurring event and storing the management data, wherein the event is a write system call in the first management device; and
skipping a data verification for continuous integrated management through a simultaneous storing when the second storing is performed by the second management device at the same time as the first storing performed.
8. The method of claim 7, wherein the first management device and the second management device are configured to synchronize the occurring event with each other.
9. The method of claim 7, wherein the second storing is performed according to a defined period when the external environment of the edge server is in a second state.
10. The method of claim 7, further comprising:
understanding, by the second management device, a state of the first management device; collecting, by the second management device, environment information of the edge server when it is understood that the first management device is in a disabled state; and managing, by the second management device, the edge server, based on the collected environmental information.
11. The method of claim 7, wherein an environment of the edge server is a rugged environment.
US17/497,183 2020-11-06 2021-10-08 Data replication processing method between management modules in rugged environment Active US12088665B2 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR1020200147256A KR102411260B1 (en) 2020-11-06 2020-11-06 Data replication process method between management modules in a rugged environment
KR10-2020-0147256 2020-11-06

Publications (2)

Publication Number Publication Date
US20220150304A1 US20220150304A1 (en) 2022-05-12
US12088665B2 true US12088665B2 (en) 2024-09-10

Family

ID=81453737

Family Applications (1)

Application Number Title Priority Date Filing Date
US17/497,183 Active US12088665B2 (en) 2020-11-06 2021-10-08 Data replication processing method between management modules in rugged environment

Country Status (2)

Country Link
US (1) US12088665B2 (en)
KR (1) KR102411260B1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102759730B1 (en) * 2022-06-30 2025-01-24 (주)다인시스 Intelligent outdoor terminal device capable of normal operation in harsh environments

Citations (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020161789A1 (en) * 2001-03-21 2002-10-31 Christian Schaefer Parallel replication mechanism for state information produced by serialized processing
US20020194276A1 (en) * 2001-06-15 2002-12-19 Kabushiki Kaisha Toshiba Distributed system and multiplexing control method for the system
US20050025179A1 (en) * 2003-07-31 2005-02-03 Cisco Technology, Inc. Distributing and balancing traffic flow in a virtual gateway
US20050198327A1 (en) * 2004-03-02 2005-09-08 Takashige Iwamura Computer system capable of fast failover upon failure
US7546366B2 (en) * 2003-05-27 2009-06-09 Nokia Corporation Data collection in a computer cluster
US20090222498A1 (en) * 2008-02-29 2009-09-03 Double-Take, Inc. System and method for system state replication
KR20090101921A (en) 2007-04-13 2009-09-29 인터내셔널 비지네스 머신즈 코포레이션 Automated firmware restoration to a peer programmable hardware device
US20100064165A1 (en) * 2008-09-11 2010-03-11 Hitachi, Ltd. Failover method and computer system
US7840992B1 (en) * 2006-09-28 2010-11-23 Emc Corporation System and method for environmentally aware data protection
US20110218967A1 (en) * 2010-03-08 2011-09-08 Microsoft Corporation Partial Block Based Backups
US8102759B2 (en) * 2004-12-07 2012-01-24 Koninklijke Philips Electronics N.V. Sensor network
US20130103977A1 (en) * 2011-08-04 2013-04-25 Microsoft Corporation Fault tolerance for tasks using stages to manage dependencies
US20130275808A1 (en) * 2010-12-21 2013-10-17 International Business Machines Corporation Techniques for Virtual Machine Management
US8966318B1 (en) * 2012-04-27 2015-02-24 Symantec Corporation Method to validate availability of applications within a backup image
US20150067084A1 (en) 2013-09-03 2015-03-05 Wistron Corporation Server system and redundant management method thereof
US9077617B1 (en) * 2012-12-21 2015-07-07 Juniper Networks, Inc. Kernel-based TCP-layer assist for fast recovery by backup control unit of a device
US20150350077A1 (en) * 2014-05-30 2015-12-03 Brocade Communications Systems, Inc. Techniques For Transforming Legacy Networks Into SDN-Enabled Networks
US20160077936A1 (en) * 2014-09-12 2016-03-17 Facebook, Inc. Failover mechanism in a distributed computing system
US20160085650A1 (en) * 2013-03-04 2016-03-24 Netapp Inc. Systems and methods for resynchronizing mirroring partners in a storage system
US9507685B2 (en) * 2013-04-03 2016-11-29 Vmware, Inc. Grouping failure events with adaptive polling and sliding window buffering
US9535806B1 (en) * 2015-03-30 2017-01-03 EMC IP Holding Company LLC User-defined storage system failure detection and failover management
US20170060694A1 (en) * 2015-08-24 2017-03-02 Acronis International Gmbh System and method for automatic data backup based on multi-factor environment monitoring
US20170242599A1 (en) * 2016-02-22 2017-08-24 Netapp Inc. Enabling data integrity checking and faster application recovery in synchronous replicated datasets
US20180062922A1 (en) * 2016-08-26 2018-03-01 Brocade Communications Systems, Inc. Application launcher and management framework for a network device
US20180337989A1 (en) * 2017-05-17 2018-11-22 Mz Ip Holdings, Llc System and method for synchronizing data between computer devices
US20180336103A1 (en) * 2017-05-17 2018-11-22 Dell Products, L.P. Concurrent upgrade of primary and standby databases
US20190278672A1 (en) * 2018-03-09 2019-09-12 Hewlett Packard Enterprise Development Lp Persistent reservation commands in a distributed storage system
US20200026440A1 (en) * 2018-07-19 2020-01-23 Hewlett Packard Enterprise Development Lp In-Flight Data Records
US20200073772A1 (en) * 2014-05-28 2020-03-05 International Business Machines Corporation Determining an availability score based on available resources at a first server to determine whether to direct processing from a first server to a second server
US20200186410A1 (en) * 2017-09-06 2020-06-11 Nec Corporation Cluster system, cluster system control method, server device, control method, and non-transitory computer-readable medium storing program
US20200195415A1 (en) * 2018-12-18 2020-06-18 Simmonds Precision Products, Inc. Distributed time synchronization protocol for an asynchronous communication system
US20200371651A1 (en) * 2019-05-24 2020-11-26 California Eastern Laboratories, Inc. User interface device updating system and method

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6070115B2 (en) * 2012-11-28 2017-02-01 日本電気株式会社 Information processing apparatus, BMC and BIOS update method
JP6148039B2 (en) * 2013-03-01 2017-06-14 Ｎｅｃプラットフォームズ株式会社 Information processing apparatus, BMC switching method, BMC switching program
JP7212510B2 (en) * 2018-12-13 2023-01-25 Ｎｅｃプラットフォームズ株式会社 Power management device, power management method, and power management program

Patent Citations (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020161789A1 (en) * 2001-03-21 2002-10-31 Christian Schaefer Parallel replication mechanism for state information produced by serialized processing
US20020194276A1 (en) * 2001-06-15 2002-12-19 Kabushiki Kaisha Toshiba Distributed system and multiplexing control method for the system
US7546366B2 (en) * 2003-05-27 2009-06-09 Nokia Corporation Data collection in a computer cluster
US20050025179A1 (en) * 2003-07-31 2005-02-03 Cisco Technology, Inc. Distributing and balancing traffic flow in a virtual gateway
US20050198327A1 (en) * 2004-03-02 2005-09-08 Takashige Iwamura Computer system capable of fast failover upon failure
US8102759B2 (en) * 2004-12-07 2012-01-24 Koninklijke Philips Electronics N.V. Sensor network
US7840992B1 (en) * 2006-09-28 2010-11-23 Emc Corporation System and method for environmentally aware data protection
KR20090101921A (en) 2007-04-13 2009-09-29 인터내셔널 비지네스 머신즈 코포레이션 Automated firmware restoration to a peer programmable hardware device
US20090222498A1 (en) * 2008-02-29 2009-09-03 Double-Take, Inc. System and method for system state replication
US20100064165A1 (en) * 2008-09-11 2010-03-11 Hitachi, Ltd. Failover method and computer system
US20110218967A1 (en) * 2010-03-08 2011-09-08 Microsoft Corporation Partial Block Based Backups
US20130275808A1 (en) * 2010-12-21 2013-10-17 International Business Machines Corporation Techniques for Virtual Machine Management
US20130103977A1 (en) * 2011-08-04 2013-04-25 Microsoft Corporation Fault tolerance for tasks using stages to manage dependencies
US8966318B1 (en) * 2012-04-27 2015-02-24 Symantec Corporation Method to validate availability of applications within a backup image
US9077617B1 (en) * 2012-12-21 2015-07-07 Juniper Networks, Inc. Kernel-based TCP-layer assist for fast recovery by backup control unit of a device
US20160085650A1 (en) * 2013-03-04 2016-03-24 Netapp Inc. Systems and methods for resynchronizing mirroring partners in a storage system
US9507685B2 (en) * 2013-04-03 2016-11-29 Vmware, Inc. Grouping failure events with adaptive polling and sliding window buffering
US20150067084A1 (en) 2013-09-03 2015-03-05 Wistron Corporation Server system and redundant management method thereof
US20200073772A1 (en) * 2014-05-28 2020-03-05 International Business Machines Corporation Determining an availability score based on available resources at a first server to determine whether to direct processing from a first server to a second server
US20150350077A1 (en) * 2014-05-30 2015-12-03 Brocade Communications Systems, Inc. Techniques For Transforming Legacy Networks Into SDN-Enabled Networks
US20160077936A1 (en) * 2014-09-12 2016-03-17 Facebook, Inc. Failover mechanism in a distributed computing system
US9535806B1 (en) * 2015-03-30 2017-01-03 EMC IP Holding Company LLC User-defined storage system failure detection and failover management
US20170060694A1 (en) * 2015-08-24 2017-03-02 Acronis International Gmbh System and method for automatic data backup based on multi-factor environment monitoring
US20170242599A1 (en) * 2016-02-22 2017-08-24 Netapp Inc. Enabling data integrity checking and faster application recovery in synchronous replicated datasets
US20180062922A1 (en) * 2016-08-26 2018-03-01 Brocade Communications Systems, Inc. Application launcher and management framework for a network device
US20180337989A1 (en) * 2017-05-17 2018-11-22 Mz Ip Holdings, Llc System and method for synchronizing data between computer devices
US20180336103A1 (en) * 2017-05-17 2018-11-22 Dell Products, L.P. Concurrent upgrade of primary and standby databases
US20200186410A1 (en) * 2017-09-06 2020-06-11 Nec Corporation Cluster system, cluster system control method, server device, control method, and non-transitory computer-readable medium storing program
US20190278672A1 (en) * 2018-03-09 2019-09-12 Hewlett Packard Enterprise Development Lp Persistent reservation commands in a distributed storage system
US20200026440A1 (en) * 2018-07-19 2020-01-23 Hewlett Packard Enterprise Development Lp In-Flight Data Records
US20200195415A1 (en) * 2018-12-18 2020-06-18 Simmonds Precision Products, Inc. Distributed time synchronization protocol for an asynchronous communication system
US20200371651A1 (en) * 2019-05-24 2020-11-26 California Eastern Laboratories, Inc. User interface device updating system and method

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
Korean Office Action issued on Mar. 7, 2022, in counterpart Korean Patent Application No. 10-2020-0147256 (3 pages in English and 5 pages in Korean).

Also Published As

Publication number Publication date
KR102411260B1 (en) 2022-06-21
US20220150304A1 (en) 2022-05-12
KR20220061366A (en) 2022-05-13

Similar Documents

Publication Publication Date Title
EP2281240B1 (en) Maintaining data integrity in data servers across data centers
US8732129B2 (en) Storage system for managing a log of access
CN110807064B (en) Data recovery device in RAC distributed database cluster system
CN100547558C (en) Method and system for redundancy protection in a parallel computing system
CN102402395A (en) Method for uninterrupted operation of high-availability system based on quorum disk
CN103294752A (en) Online verification method and system of a standby database in log shipping physical replication environment
CN102546135A (en) System and method for switching between active and standby servers
US8527454B2 (en) Data replication using a shared resource
CN114189429B (en) Monitoring system, method, device and medium for server cluster faults
CN105607973A (en) Method, device and system for processing equipment failures in virtual machine system
CN109445988A (en) Isomery disaster recovery method, device, system, server and disaster recovery platform
US12088665B2 (en) Data replication processing method between management modules in rugged environment
CN110968456B (en) Method and device for processing fault disk in distributed storage system
CN113849350B (en) Ring two-site three-center topology switching method, device, system and medium
JPH05120110A (en) File automatic backup system
CN112015600A (en) Log information processing system, log information processing method and device and switch
CN102929761A (en) System and method for responding corruption error
CN112732492A (en) Extraction backup method and system based on cloud database
JP2018180982A (en) INFORMATION PROCESSING APPARATUS AND LOG RECORDING METHOD
CN106599046B (en) Writing method and device of distributed file system
JP2009282735A (en) Information recording system and information recording method
CN119226405B (en) Method for synchronizing data of master database and slave database
US20220308563A1 (en) Controller and control method
CN112596941B (en) Tool result judging method and device of industrial image processing software
CN119128010A (en) Bidirectional data synchronization method, computer program product, device and storage medium

Legal Events

Date Code Title Description
AS Assignment

Owner name: KOREA ELECTRONICS TECHNOLOGY INSTITUTE, KOREA, REPUBLIC OF

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:AN, JAE HOON;KIM, YOUNG HWAN;REEL/FRAME:057758/0800

Effective date: 20211007

FEPP Fee payment procedure

Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY

FEPP Fee payment procedure

Free format text: ENTITY STATUS SET TO SMALL (ORIGINAL EVENT CODE: SMAL); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: FINAL REJECTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: ADVISORY ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: ADVISORY ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: FINAL REJECTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE AFTER FINAL ACTION FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS

ZAAB Notice of allowance mailed

Free format text: ORIGINAL CODE: MN/=.

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT RECEIVED

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED

STCF Information on status: patent grant

Free format text: PATENTED CASE