Description:FIELD OF INVENTION
[0001] The present invention relates generally to content management systems, and more specifically to a distributed content management system with local caching and intelligent synchronization for efficient content access and management in low-bandwidth and geographically distributed environments. The invention further relates to a method for uploading, retrieving, and synchronizing electronic contents within such a system.
BACKGROUND OF INVENTION
[0002] In today's business environment, effective content management is essential for ensuring smooth operations and productivity. Organizations operating across geographically dispersed locations, however, often encounter significant challenges in ensuring seamless content retrieval and access due to inherent network bandwidth limitations. Traditional centralized cloud-based storage solutions, such as Amazon S3 and Azure blob , while offering scalability and cost-effectiveness, may not always align with the stringent data governance and compliance requirements of certain enterprises, particularly those mandated to maintain on-premises data storage. Furthermore, relying solely on cloud-based storage for geographically distributed access can introduce latency and performance bottlenecks, especially in regions with constrained network connectivity.

[0003] Existing content management solutions often suffer from the following limitations:
High Network Dependency: These systems exhibit a strong dependence on stable and high-bandwidth network connections, rendering them vulnerable to network outages or congestion. This dependency can significantly impede content access and workflow continuity in low-bandwidth or intermittently connected environments.
Latency and Access Delays: Accessing content from remote locations via centralized servers can introduce substantial latency, particularly when dealing with large files or during periods of high network traffic. This latency translates to delays in document retrieval, negatively impacting user productivity and overall operational efficiency.

[0004] Lack of Intelligent Synchronization: Current solutions often lack sophisticated mechanisms for intelligent synchronization of content across multiple locations. This can result in inefficient bandwidth utilization, with redundant data transfers or delays in propagating content updates, leading to inconsistencies across different locations.

[0005] Balancing Local Access and Centralized Consistency: A key challenge lies in balancing the need for local content storage and management (for rapid access) with the requirement for maintaining data consistency and version control across all locations. Existing solutions frequently struggle to achieve this balance effectively.

[0006] Scalability and Cost Considerations: While cloud-based solutions offer scalability, they can also introduce unpredictable cost structures, especially for organizations with large content volumes or high access frequencies. On-premises solutions, while potentially offering more control, may lack the inherent scalability of cloud-based offerings.

[0007] Compliance and Security: Certain industries and organizations are subject to strict regulatory requirements regarding data residency and security. These compliance mandates often necessitate on-premises data storage, making cloud-based solutions unsuitable. Existing systems may not adequately address these specific compliance and security concerns.

[0008] The present invention aims to overcome these limitations by introducing a hybrid document storage and synchronization system that strategically combines local caching with intelligent background synchronization. This approach optimizes document accessibility for geographically distributed users while ensuring data consistency across the enterprise and adhering to on-premises data storage requirements. The proposed system addresses the challenges of limited bandwidth, latency, and compliance by providing a robust and scalable solution operable to electronic content in distributed environments.

OBJECTIVES OF THE INVENTION

[0009] The primary objective of the invention is to provide a distributed content management system that enables efficient content access and management in low-bandwidth and geographically distributed environments.

[0010] Another objective of the invention is to reduce reliance on high-bandwidth network connections for content access by leveraging local storage at remote locations.

[0011] A further objective of the invention is to minimize latency and improve response times for content retrieval by prioritizing local access.

[0012] Still another objective of the present invention is optimize bandwidth usage by implementing intelligent synchronization mechanisms.

[0013] Yet another objective of the invention is to ensure data consistency and integrity across all locations while maintaining local control and management.

BRIEF SUMMARY OF THE INVENTION

[0014] In the following detailed description, reference is made to the accompanying drawings that form a part hereof, and in which the specific embodiments that may be practiced is shown by way of illustration. These embodiments are described in sufficient detail to enable those skilled in the art to practice the embodiments and it is to be understood that the logical, mechanical, and other changes may be made without departing from the scope of the embodiments. The following detailed description is therefore not to be taken in a limiting sense.

[0015] The foregoing of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments.

[0016] The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any alterations, equivalents, and substitutes in addition to those which are particularly set out in the accompanying drawings.

[0017] In accordance with one embodiment, the present invention provides a distributed content management system that optimizes content storage, retrieval, and synchronization across multiple geographical locations while minimizing bandwidth usage. The system includes a central server responsible for storing and managing content metadata. This server receives metadata from remote image servers during uploads and provides metadata and document lists to remote image servers when retrieval requests are made.

[0018] With reference to another embodiment, the system comprises geographically distributed remote image servers that communicate with the central server. Each remote image server processes content uploads by receiving files from users, storing them locally, and transmitting metadata to the central server. The remote servers also handle document retrieval requests by locating and delivering stored document files to users, ensuring quick access with minimal reliance on network bandwidth.

[0019] According to yet another embodiment, the system includes a synchronization mechanism that facilitates content file replication between the remote servers and the central server. The synchronization process is governed by a Replicate Scheduler Service, which operates based on predefined configurations and executes during non-production hours to optimize bandwidth usage.

[0020] In some embodiments, the system employs a smart replication process that dynamically adapts to available network bandwidth, ensuring efficient data transfer while preventing network congestion.

[0021] In accordance with certain embodiments, the synchronization mechanism is configurable based on predefined parameters, such as scheduled replication intervals,Content modification timestamps, or access frequency to prioritize critical data.

[0022] In an alternate embodiment, the central metadata server comprises an access control module to regulate user permissions, ensuring that only authorized individuals can access specific contents.

[0023] In some embodiments, each remote image server maintains a local cache for frequently accessed document/content files, enhancing retrieval efficiency and reducing redundant requests to the central metadata server.

[0024] According to another embodiment, all communication between the remote servers and the central server is secured using a secure communication protocol, ensuring confidentiality and integrity in data exchange.

[0025] With reference to further embodiments, each document's metadata includes file type, author, creation date, access permissions, and a unique identifier, allowing precise tracking and management within the system.

[0026] In accordance with one aspect, the Replicate Scheduler Service may be deployed on the central server or one of the remote image servers, offering deployment flexibility based on system requirements.

[0027] In certain embodiments, the synchronization mechanism is event-driven, where synchronization is triggered by factors such as network bandwidth availability or direct user requests, allowing real-time adaptability.

[0028] With reference to another embodiment, the system enhances security by encrypting document files stored on remote document servers, ensuring unauthorized access is prevented. Additionally, document metadata stored on the central server is encrypted, further safeguarding sensitive information.

[0029] In light of the foregoing embodiments, the present invention provides a scalable, secure, and bandwidth-efficient content management system, ensuring seamless access and synchronization of content across multiple locations while maintaining data integrity and security.

BRIEF DESCRIPTION OF DRAWINGS

[0030] Figure 1 illustrates the system architecture of the Remote Image Server (RIS) system, showing the interaction between users, the Central Server, and multiple Remote Image Servers.

[0031] Figure 2 illustrates the process flow for uploading and storing a document within the RIS system, depicting the interaction between the user, the Remote Image Server, and the Central Server.

[0032] Figure 3 illustrates the process flow for retrieving and viewing a document within the RIS system, showcasing the steps involved in fetching the document list, retrieving metadata, and accessing the document content.

[0033] Figure 4 illustrates the process flow for replicating documents from a Remote Image Server to the Central Server, outlining the steps involved in scheduling, executing, and completing the replication process.

[0034] Further, those skilled in the art will appreciate that elements in the figures are illustrated for simplicity and may not have necessarily been drawn to scale. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the figures by conventional symbols, and the figures may show only those specific details that are pertinent to understanding the embodiments of the present disclosure so as not to obscure the figures with details that will be readily apparent to those skilled in the art having the benefit of the description herein.

DETAILED DESCRIPTION OF THE INVENTION

[0035] The following figures illustrate various aspects of the Remote Image Server (RIS) system, including its architecture, document upload process, document retrieval process, and the document replication process.

[0036] The figure 1 (100) presents an overview of the RIS system architecture, showcasing the interaction between users (102a, 102b, 102c), the Central Server (104), and multiple Remote Image Servers (106a, 106b). The Central Server (104) acts as the central hub for metadata management, handling "Add or view document operation" and serving as the "Central document operation" point. It is responsible for "Meta data store while add document operation" and "Meta data retrieval while view document operation." Two Remote Image Servers (106a, 106b), each geographically distributed and responsible for storing actual document files. They also handle "Add or view document operation," "Meta data store while add document operation," and "Meta data retrieval while view document operation." wherein one of the Users (102a) at the interact directly with the Central Server (104), while other users (102b, 102c) interact with their local Remote Image Servers (106a, 106b). Arrows illustrate data flow: replication arrows connect the Central Server (104) to the Remote Image Servers (106a, 106b), labelled "Actual file replication during non-production hours"; local access arrows connect users (102b) to their respective Remote Image Servers (106a, 106b). Components labelled "SMS" (108) are connected to both the Central Server (104) and the Remote Image Servers (106a, 106b), suggesting potential SMS integration for notifications or alerts..

[0037] The figure 2 (200) details the steps involved in uploading and storing a document. The process begins with the Application User (202) initiating the upload ("Add Document"). The document is transmitted to the Remote Image Server (204), which performs two actions: storing the actual document file into "Storage management server (SMS)" (206) and transmitting the document's metadata to the Central Server (208) ("Document Meta Data Stored"). The Central Server (208) then stores the metadata into its database (210) ("Meta data Stored into Database"), concludes with a confirmation ("Document Stored Successfully" (212)), reiterating that the metadata is stored centrally while the document resides on the Remote Image Server (204).

[0038] The figure 3 (300) illustrates the document retrieval process. The Application User (302) requests to view a document ("To view the document, click on the folder"), triggering a request to the Remote Image Server (304) ("Document List required"). The Remote Image Server (304) queries the Central Server (306), which provides the document list (308) and the document's metadata (310). The Remote Image Server (304) then retrieves the actual document from "RIS SMS" (312) ("Actual document retrieve from RIS SMS"). The process concludes with the user successfully viewing the document ("View Document Successfully" (314)), with labels indicating that metadata is retrieved from the central server and the document from the remote server.

[0039] The figure 4 (400) outlines the document replication process. The process begins with "Document Replicate Started" (402). "Step 1" involves the "Replicate Scheduler Services" (404). "Step 2" describes the replication based on pre-defined configurations. The Remote Image Server (406) then replicates the eligible documents to the Central Server (408) in "Step 3." The process completes with "Replication Completed" (410).

DETAILED DESCRIPTION

[0040] For the purpose of promoting an understanding of the principles of the disclosure, reference will now be made to the embodiment illustrated in the figures and specific language will be used to describe them. It will nevertheless be understood that no limitation of the scope of the disclosure is thereby intended. Such alterations and further modifications in the illustrated system, and such further applications of the principles of the disclosure as would normally occur to those skilled in the art are to be construed as being within the scope of the present disclosure.

[0041] The terms “comprise”, “comprising”, or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such a process or method. Similarly, one or more devices or subsystems or elements or structures or components preceded by "comprises... a" does not, without more constraints, preclude the existence of other devices, sub-systems, elements, structures, components, additional devices, additional sub-systems, additional elements, additional structures or additional components. Appearances of the phrase "in an embodiment", "in another embodiment" and similar language throughout this specification may, but not necessarily do, all refer to the same embodiment.

[0042] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this disclosure belongs. The system, methods, and examples provided herein are only illustrative and not intended to be limiting.

[0043] The present invention relates to a distributed document management system (100) operable to documents in low-bandwidth, geographically distributed environments. The system addresses the limitations of traditional centralized document management systems, such as high network dependency, latency, and limited control over data storage.

[0044] As illustrated in Figure 1, the core of the invention lies in a distributed architecture comprising: Central Metadata Server (104): This server acts as the central repository for document metadata, including information such as document name, author, creation date, modification history, and access permissions. The Central Server (104) receives document metadata from Remote Image Servers (106a, 106b) during document uploads (200) and provides document metadata (310) and document lists (308) to Remote Image Servers (106a, 106b) during document retrieval requests (300). This centralized metadata management enables efficient search, filtering, and access control across the entire system.

[0045] Further Remote Image Servers (106a, 106b) servers are geographically distributed, located closer to users in different locations. Each Remote Image Server (106a, 106b) stores the actual document files, enabling local access and minimizing the need for frequent data transfers over the network. This distributed storage approach significantly reduces latency and improves access speed for users.

[0046] The document management workflow is illustrated in figure 2. wherein a user uploads a new document, the process begins with the User (202) initiating the upload. The document is then transmitted to the Remote Image Server (204), where it is stored in the Single central server SMS system (206). Simultaneously, the Remote Image Server (204) transmits the document's metadata to the Central Server (208). The Central Server (208) then stores this metadata in its database (210).

[0047] Figure 3 illustrates the document retrieval process. when the User (302) initiates the retrieval process, the Remote Image Server (304) queries the Central Server (306) for the document list (308) and the associated metadata (310). The Remote Image Server (304) then retrieves the actual document file (312) from the Single central server SMS system (312) and presents it to the Application User (302).

[0048] Further, to ensure data consistency across the system, a robust synchronization mechanism is implemented. As illustrated in figure 4, the process is initiated by the Replicate Scheduler Service (404). This service determines which documents need to be replicated based on pre-defined configurations (404), such as time schedules, document modification timestamps, or user-defined rules. The selected documents are then transferred from the Remote Image Servers (106a, 106b) to the Central Server (408) during non-production hours to minimize network congestion and disruption to user operations.

[0049] In another embodiment, the system prioritizes local access to documents whenever possible. By storing documents on the local Remote Image Server (106a, 106b), the system minimizes the need for users to access documents over the network, reducing latency and bandwidth consumption. This approach significantly improves user experience and enhances overall system performance, especially in low-bandwidth environments.

[0050] Further, the Central Server (104) serves as the central repository for all document metadata. Furthermore, it receives and stores metadata, including document name, author, and creation date, from each Remote Image Server (106a, 106b) during document uploads (Figure 2). The Central Server (104) also provides document metadata (310) and document lists (308) to Remote Image Servers (106a, 106b) upon document retrieval requests. Additionally, it manages access control and permissions to ensure secure document access and coordinates the synchronization process with the Remote Image Servers to maintain data consistency.

[0051] In one of the embodiments, the Remote Image Servers (106a, 106b) are geographically distributed and function as storage units for actual document files, ensuring faster access for users and reducing network latency. These servers handle document uploads and retrievals while maintaining synchronization with the Central Server (104). They receive and store documents uploaded by users (204), transmit document metadata to the Central Server (208) during document uploads (200), and handle document retrieval requests (302) by delivering requested documents to users (312). Additionally, they participate in document replication, sending and receiving data from the Central Server (104), and provide local access to documents to optimize performance and reduce bandwidth usage.

[0052] In one of the embodiments, the Application User (202, 302) interacts with the system to upload and retrieve documents efficiently. The system ensures seamless accessibility to document storage and retrieval processes, allowing users to manage files without latency issues. Users upload documents to the Remote Image Server (204), retrieve and view documents from the Remote Image Server (304), and initiate document retrieval requests, which are processed through the system to ensure seamless access.

[0053] In one of the embodiments, the Replicate Scheduler Service (404) is responsible operable to and automating the document synchronization process between the Remote Image Servers (106a, 106b) and the Central Server (104). This ensures that all stored content remain updated across multiple locations. The scheduler identifies documents that need replication based on predefined configurations, including time schedules and modification dates, initiates the data transfer process between Remote Image Servers (106a, 106b) and the Central Metadata Server (104), and ensures efficient and timely synchronization to maintain consistency across multiple servers.

[0054] In one of the embodiments, Storage management server SMS (206, 312) serves as the primary storage system within the Remote Image Servers (106a, 106b), ensuring that document files are securely maintained while allowing efficient retrieval operations. It receives and stores uploaded documents, delivers documents to users upon request, and participates in the data replication process to ensure seamless data transfer between Remote Image Servers and the Central Server.

[0055] In one of the embodiments, the document upload process is initiated when a user uploads a document (202). The Remote Image Server (204) stores the document in the Storage management server SMS system (206) and transmits metadata to the Central Server (208) for centralized tracking and management.

[0056] In one of the embodiments, the document retrieval process is initiated when a user submits a retrieval request (302). The Remote Image Server (304) queries the Central Server (306) for metadata (310) and retrieves the requested document file (312) from Storage management server SMS (312) before delivering it to the user.

[0057] In one of the embodiments, the Replicate Scheduler Service (404) initiates the content synchronization process, ensuring that eligible contents are transferred from the Remote Image Servers (106a, 106b) to the Central Server (408) based on predefined conditions.

[0058] In one of the embodiments, the Central Server (104) ensures data consistency across all connected Remote Image Servers (106a, 106b) by managing document metadata, overseeing synchronization, and ensuring that all storage locations remain up to date with the latest document versions.

[0059] Advantages:
• Distributed Architecture: The distributed architecture with geographically dispersed Remote Image Servers (106a, 106b) enables efficient content management across multiple locations.
• Local Access Prioritization: Prioritizing local access minimizes network dependency and improves access speed for users.
• Intelligent Synchronization: The synchronization mechanism ensures data consistency while optimizing bandwidth usage by replicating content strategically.
• Enhanced Performance: The system addresses challenges associated with traditional centralized systems, such as latency and network congestion, leading to improved overall performance and user experience.
• Flexibility and Scalability: The system can be easily scaled to accommodate growing data volumes and increasing user demands by adding new Remote Image Servers (106a, 106b) as needed.
• Compliance and Security: The system can be operable to meet various compliance requirements, such as on-premises data storage and security regulations, by leveraging the distributed architecture and local storage capabilities.
[0060] It will be understood by those skilled in the art that the foregoing general description and the following detailed description are exemplary and explanatory of the disclosure and are not intended to be restrictive thereof.

[0061] The figures and the foregoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, the order of processes described herein may be changed and are not limited to the manner described herein. Moreover, the actions of any flow diagram need not be implemented in the order shown; nor do all of the acts need to be necessarily performed. Also, those acts that are not dependent on other acts may be performed in parallel with the other acts. The scope of embodiments is by no means limited by these specific examples.
, C , C , Claims:1. A distributed content management system (100) operable to manage content in a low-bandwidth, geographically distributed environment, the system comprising:
a central server (104) operable to store and manage content metadata, including receiving content metadata from remote image servers (106a, 106b) during document uploads (200) and providing document metadata (310) and document lists (308) to remote image servers (106a, 106b) during document retrieval requests (300);
a plurality of geographically distributed remote image servers (106a, 106b) in communication with the central server (104), each remote image server (106a, 106b) operable to:
a. receive document upload requests (202) from users (202);
b. store document files (206) in a storage system associated with the respective remote image server (106a, 106b);
c. transmit document metadata to the central server (208) during document uploads (200);
d. receive document retrieval requests (302) from users (302); and
e. retrieve document files (312) from the associated storage system during document retrieval requests (300);
a synchronization mechanism operable to synchronize content files between the remote image servers (106a, 106b) and the central server (104), the synchronization being initiated by a Replicate Scheduler Service (404) and based on pre-defined configurations (404), the synchronization occurring during non-production hours.
wherein the system prioritizes local access to document files by users (102a, 102b,102c) via the respective geographically distributed remote image server (106a, 106b) to improve access speed and reduce bandwidth consumption; and
wherein the storage system associated with each remote image server (106a, 106b) is a Storage management server (SMS) system (206, 312).
2. The system as claimed in claim 1, wherein the synchronization mechanism employs an adaptive smart replication process that adapts to available network bandwidth.

3. The system as claimed in claim 1, wherein the pre-defined configurations for the synchronization process include a schedule for replication.

4. The system as claimed in claim 1, wherein the pre-defined configurations for the synchronization process include criteria for selecting document files based on their modification date and (or) access frequency.

5. The system as claimed in claim 1, wherein the central metadata server (104) comprises an access control module operable to user access to documents.

6. The system as claimed in claim 1, wherein each remote document server (106a, 106b) comprises an SMS which acts as a local cache for frequently accessed document files.

7. The system as claimed in claim 1, wherein the remote document servers (106a, 106b) and the central metadata server (104) communicate using a secure communication protocol.

8. The system as claimed in claim 1, wherein the document metadata includes information about document type, author, creation date, access permissions, and a unique identifier for the document file.

9. The system as claimed in claim 1, wherein the Replicate Scheduler Service (404) is located on the central server.

10. The system as claimed in claim 1, wherein the Replicate Scheduler Service (404) is located on at least one of the remote image servers (106a, 106b).

11. The system as claimed in claim 1, wherein the synchronization mechanism is triggered by an event.

12. The system as claimed in claim 1, wherein the event is a change in the availability of network bandwidth.

13. The system as claimed in claim 1, wherein the event is a user request.

14. The system as claimed in claim 1, wherein the document files stored on the remote image servers (106a, 106b) are encrypted.

15. The system as claimed in claim 1, wherein the document metadata stored on the central server (104) is encrypted.